Service developer documentation
Two products, documented separately. The widget takes bookings in the browser. The API reads reservation and guest data on your server.
Widget Embed a booking form on a website, or drive one from your own code. Runs in the browser. No API key.
API Read reservations and guests, and receive webhooks. Runs on your server. Authenticated, read-only.
Which one applies
Section titled “Which one applies”| Widget | API | |
|---|---|---|
| Runs in | The guest’s browser | Your server |
| Authentication | None | sk_live_… API key |
| Operations | Creates bookings | Reads bookings and guests |
| Integrated by | A front-end developer, or by pasting a snippet | A back-end developer |
Most integrations use both. The widget takes the booking; the API and its webhooks report it to other systems.