Booking Intake API.
Feed booking requests from your own website straight into your review queue. Auth via a per-key X-API-Key header - not a session token.
One header. One key per integration.
Six endpoints. The core flow is one.
/api/v1/bookings/submitSubmit a booking request from your own site. Auth: X-API-Key.
/api/v1/bookings/pendingList bookings awaiting your review. Auth: your logged-in session.
/api/v1/bookings/{booking_request_id}/acceptAccept a pending booking. Fires the booking.accepted webhook if one's configured. Auth: your logged-in session.
/api/v1/bookings/{booking_request_id}/declineDecline a pending booking. Fires booking.declined. Auth: your logged-in session.
/api/v1/booking-api-keys/webhookSet (or clear) the URL that receives accept/decline events. Auth: your logged-in session.
/api/v1/booking-api-keys/mintMint your own API key from your account settings, after accepting the API terms. Auth: your logged-in session.
Signed, opt-in, and never the source of truth.
Configuring a webhook is optional - nothing breaks if you never set one, you'd just poll /bookings/pending instead. If a webhook delivery fails, the accept/decline itself already happened; the webhook is a notification, not a transaction.
Every delivery attempt is logged on our side (URL, status code, success) whether or not yours succeeds - so a missed webhook is something we can actually look into together, not a mystery.
Where your submitted bookings appear.
Every booking your site submits shows up in the Bookings queue as "Website API", ready for your team to quote. When they accept it, your site gets the signed webhook.
