Skip to content
Booking Engine API Docs

Webhooks

Not shipped yet. Outbound webhooks are tracked as API-014 (Phase 4). GET/POST/DELETE /v1/webhook-endpoints exists in the public API design, but nothing is deployed yet.

Until webhooks ship, poll the relevant read endpoint — for example GET /v1/bookings/{id}, which is live today — instead of waiting for a push notification.

What’s planned

Section titled “What’s planned”
  • Register an endpoint URL; we deliver events to it over HTTPS.
  • Every delivery is HMAC-signed — you’ll verify the signature before trusting a payload, the same convention Stripe uses.
  • Delivery is queued, with retries and a dead-letter queue for endpoints that keep failing.
  • Each event carries a stable external id; process it with an idempotent handler on your side (ON CONFLICT DO NOTHING or equivalent) — a redelivered event is not a second booking.

This page gets a real signature-verification example and a real event payload the day the first webhook event type ships.