Developer Overview
The core public surfaces are already clear enough to organize around: booking routes, widget routes, webhooks, and agent-oriented integrations.
Public booking flow
Use tenant-based availability and booking routes when you want a direct booking experience without the widget layer.
View route index →Widget flow
Use widget config, availability, and booking endpoints when the booking experience is embedded on a site or launched from a direct widget link.
See widget endpoints →Webhooks
Booking lifecycle events can be delivered with signing and retry behavior for downstream systems.
Review webhook notes →AI and agent integrations
Advanced teams can use MCP and UCP surfaces for agent-driven booking workflows without making that the main product story for every buyer.
Open integration page →Current Integration Shape
Base path
/booking-core/apiMain public surfaces
- Tenant availability and booking endpoints
- Widget config, availability, and booking endpoints
- Webhook delivery infrastructure
- MCP and UCP integration paths
Need Help With An Implementation?
If you already know you need APIs, webhooks, or agent integrations, contact us with the workflow you are trying to support and we can point you to the fastest starting path.