Webhooks

Outbound webhooks are coming soon. RentBridge does not yet push events to your endpoints — this page explains what exists today and how to build event-driven integrations in the meantime.

What Exists Today

Inbound: Stripe Webhooks

RentBridge itself consumes Stripe webhooks (POST /api/v1/billing/webhook, signature-verified) to keep your subscription status in sync. This is internal plumbing — you don't need to configure anything.

Polling the API

Until outbound webhooks ship, poll the REST API for changes:

# New or changed rentals
GET /api/v1/rentals?status=returned

# Fleet alerts (overdue returns, maintenance due, low utilization)
GET /api/v1/fleet/alerts

# Settlements awaiting payout
GET /api/v1/settlements?payout_status=pending

Practical polling pattern:

• Poll every 1–5 minutes (well within the 100 req/min rate limit)
• Track the IDs you've already processed to detect what's new
• Use list filters (status, payout_status) to keep responses small

See API Overview for authentication and the full endpoint list.

Planned Webhook Events

When outbound webhooks ship, expect events along these lines (subject to change):

Event	When it fires
rental.transitioned	A rental moves through the booking flow (reserved, active, returned, closed, cancelled)
settlement.created	A returned rental is settled
settlement.paid	An owner payout completes
deposit.released / deposit.forfeited	A deposit escrow decision is made
insurance.purchased	A renter binds a policy
maintenance.predicted	The maintenance agent flags a unit

Planned delivery semantics: JSON POST to your HTTPS endpoint, unique event IDs for idempotency, signature verification, and automatic retries.

Want to be notified when webhooks launch — or influence which events ship first? Email support@rentbridge.ai.

Support

Contact support via the Help icon in your dashboard or email support@rentbridge.ai.