Class booking API.
Build a fully custom booking experience on a REST API. Read your events, create multi-spot bookings, validate promo codes, and redeem gift cards, all on scoped, origin-restricted keys with idempotent requests behind them.
For: developers and product teams building a custom booking flow, a mobile app, or a deep integration on top of their class schedule.
The same booking engine, exposed as a REST API.
When the hosted page and the embeddable widget are not enough, the API gives you direct access to the booking engine. It covers the whole flow: reading availability for classes and courses, reserving and paying for spots, validating gift cards and promo codes, and working with the people booking.
Use public keys in the browser (a request Origin header is checked against the domains you allow) and secret keys on your server. Every key carries its own scopes, so a key only does what you grant it. Booking requests take an idempotency key, and spots lock during checkout, so retries never double-book.
River Studio workshops
Handmade Pasta
6:30 PM with Elena Martinez
Weekend Wheel Throwing
10:00 AM with Sam Okafor
Kids Science Camp
1:00 PM with Priya Shah
Complete booking
No account password. Confirmation by email.
When off-the-shelf booking is not enough.
If you have hit the limits of a hosted page or a generic embed, an API is the way out.
Bolted-on iframes
A booking embed that never quite matches your product or your design system.
No native app path
Booking that lives only on the web, with no clean way into a mobile app.
Manual data exports
Copying events and customers between systems instead of reading them live.
Risky browser keys
Front-end credentials that work from anywhere, with no origin or scope limits.
Double-booked spots
Retries and refreshes that quietly book the same spot twice during checkout.
Undocumented endpoints
Guessing at request shapes because there is no real reference to build against.
A REST API for the whole booking flow.
- Public REST endpoints. Availability for classes and courses, bookings, gift cards, promo codes, and customers.
- Public & secret keys. Origin-restricted public keys for the browser; secret keys for your server.
- Per-key scopes. Grant each key only the access it needs, and set the origins it is allowed to call from.
- Idempotency keys. Safe retries on booking requests, with spot locks so the same spot is never sold twice.
- Rate limits. Validation and read endpoints are rate-limited to keep your booking flow stable.
- Origin checks. Public keys with allowed origins reject browser requests whose Origin header is not on the list.
- OpenAPI 3.1 spec. A complete, downloadable OpenAPI 3.1 specification you can generate typed clients from, so you build against a real reference instead of guessing.
A custom booking flow, end to end.
Create your keys
Generate a public key with allowed origins for the browser, and a scoped secret key for your server.
Read upcoming events
Read upcoming events to show real availability inside your own interface or app.
Validate and book
Check promo codes and gift cards, then send the booking with an idempotency key to lock spots and capture payment.
Confirm and follow up
Customers get the usual confirmation and reminder emails; you see every booking in the same admin and reports.
Related features
Build your own booking experience.
Start taking bookings in minutes. Publish a booking page, embed the widget, or build on the API.
30-day free trial · Cancel anytime