Skip to main content

Developer platform

Build with the operation,
not around it.

Integrate booking, availability, clients, commerce and venue operations through documented contracts designed for tenant-aware products.
Open API referenceDiscuss a partnership
  • OpenAPI 3.1 reference
  • Scoped API keys
  • Signed event delivery
bookingbible.com/developers/reference
GET/api/v1/calendar

Unified calendar feed

Classes, appointments, private events, streams, unavailable time, room rentals, maintenance and shifts in one date range.

JWT or API keyread:calendarDate-range filtersVenue scoped
478
REST route handlers
458
Active webhook events
28
Embed surfaces

Choose the right boundary

Hosted when you want speed. Composable when you need control.

Use one surface or combine them. Availability and scopes depend on the venue's plan, modules and granted permissions.

478 route handlers

REST API

Versioned venue, client, booking, schedule, staff, commerce and reporting routes with an OpenAPI 3.1 reference.

Explore this surface →
458 active event types

Signed webhooks

React to booking, payment, pass, course and operational events with retryable HMAC-signed delivery.

Explore this surface →
28 embed surfaces

Embeddable experiences

Place selected public journeys into an existing site while preserving venue theme, locale and consent context.

Explore this surface →
Read-only v1

MCP server

Let approved AI clients read venue data through a deliberately read-only v1 surface with API-key scope enforcement.

Explore this surface →

Concrete contracts

Start from a documented resource

The interactive reference is generated from the API registry used by the product. Request methods, authentication modes, scopes, parameters and examples stay together.

Browse the referenceCheck API status
bash
curl "https://bookingbible.com/api/v1/calendar?start=2026-08-01&end=2026-08-07" \
  -H "X-API-Key: bb_live_…" \
  -H "X-Organization-ID: org_…"

Event-driven integrations

Know when the venue changes

Subscribe to the event types your system owns. Signed payloads and delivery retries let partner systems process changes without polling every resource.

  • Select only the events you need
  • Verify the raw payload before processing
  • Return success quickly and process asynchronously
  • Use event and resource IDs to deduplicate work
Read the webhook guide →
json
{
  "id": "evt_…",
  "type": "booking.created",
  "created_at": "2026-08-01T08:15:00Z",
  "organization_id": "org_…",
  "data": {
    "booking_id": "booking_…",
    "status": "confirmed"
  }
}

Integration quality

The boring parts are product features

A credible partner integration needs authorization, retry behavior and traceability—not only a successful demo request.

Least-privilege access

API keys carry explicit scopes. Venue context and role checks remain part of the request boundary.

Safe retry semantics

Mutation contracts use idempotency where duplicate work would create bookings, messages or financial side effects.

Verifiable delivery

Webhook signatures, delivery history and correlation identifiers support investigation and reconciliation.

Interactive reference

Inspect methods, scopes and schemas generated from the route registry.

Webhook guide

Configure endpoints, verify signatures and design a reliable consumer.

MCP guide

Connect a supported AI client to the read-only venue data surface.

Build together

Bring us the integration contract

For marketplaces, accounting systems, access control, branded apps or operational platforms, we can map ownership, data flow, security and rollout before implementation begins.

Discuss an integrationReview trust controls