Booking API

Bookora is a Cloudflare-native scheduling platform that turns availability into bookings. The Booking API lets third-party developers build scheduling experiences for meetings, lessons, consultations, and marketplaces.

• Scheduling infrastructure: availability → slots
• Calendar integration: Google / Microsoft are abstracted behind a unified layer
• Safety: lock layer + database overlap checks prevent double booking

Send your service token as a Bearer token.

All POST endpoints require Idempotency-Key. This prevents duplicate bookings when your system retries a request due to timeouts, deploys, or network errors.

• Same key + same request → same result
• Same key + different request → 409 conflict

Fetch available booking slots for a booking type.

{
  "slots": [
    {
      "start": "2026-04-21T09:00:00Z",
      "end": "2026-04-21T09:30:00Z"
    }
  ]
}

Create a booking for a specific booking type.

Each booking must be associated with a booking type, which defines duration, availability, and rules.

Call this after your user confirms (or completes payment).

{
  "bookingType": "string",
  "start": "ISO datetime",
  "end": "ISO datetime",
  "name": "string",
  "email": "string",
  "notes": "string (optional)"
}

{
  "bookingId": "uuid",
  "status": "confirmed"
}

Fetch booking details by booking ID.

{
  "id": "uuid",
  "userId": "teacher123",
  "startUtc": "2026-04-21T09:00:00Z",
  "endUtc": "2026-04-21T09:30:00Z",
  "status": "confirmed",
  "attendee": { "email": "user@example.com", "name": "Tom" }
}

Cancel a booking and remove associated calendar events (when applicable).

{
  "status": "cancelled"
}

Reschedule an existing booking to a new time safely (create a new booking, then cancel the old one).

{
  "newSlot": {
    "start": "2026-04-22T09:00:00Z",
    "end": "2026-04-22T09:30:00Z"
  }
}

{
  "oldBookingId": "uuid",
  "newBookingId": "uuid",
  "status": "rescheduled"
}

Errors use a structured envelope.

{
  "error": {
    "code": "SLOT_NOT_AVAILABLE",
    "message": "Selected time slot is no longer available"
  }
}

Requests are rate-limited per IP and per service token. Handle 429 responses with exponential backoff and jitter.

Future support may include webhooks for:

• booking.created
• booking.cancelled
• booking.rescheduled

1. Fetch availability
2. User selects a slot
3. Payment completes (if applicable)
4. Create the booking with POST /api/bookings

• Always send Idempotency-Key on POST requests
• Always store bookingId as your durable reference
• Use UTC timestamps (Z) and handle slot conflicts gracefully
• Retry safely on rate limits and transient failures