Developer: API, webhooks & embed

DayOtter is API-first: everything the UI does, it does through the same endpoints you can call. Use the REST API to read and write bookings, event types, and availability; webhooks to react to events; and the embed widget to put booking on your own site.

API keys

1. Go to Settings → Developer and create an API key.
2. Send it as a bearer token: Authorization: Bearer <key>.
3. Call the /api/v1 endpoints for bookings, event types, availability, and more.

Temporary holds

Need to reserve a slot while you take payment or finish a signup in your own app? POST /api/v1/holds to hold a slot for a few minutes (default 5, up to 30). The slot is locked the instant the hold is created, so nobody else can book it. When your flow succeeds, POST /api/v1/holds/{uid}/confirm to turn the hold into a real booking (calendar, reminders, and emails all fire then); if it fails, DELETE /api/v1/holds/{uid} to release it early. An unconfirmed hold lapses on its own and frees the slot. Confirm and release are idempotent, so a retried call is always safe.

Webhooks

Register an endpoint URL and subscribe to booking.created, booking.rescheduled, and booking.cancelled. Each delivery is signed with an HMAC-SHA-256 signature over a timestamped body (Stripe-style), so you can verify authenticity and reject replays. Deliveries retry with backoff and record their terminal status.

Embed

Drop the booking widget onto your own page so people book without leaving your site. The public booking pages are also just URLs, so you can link or iframe them anywhere.