Class booking API.
Build your own checkout on a REST API. Read the schedule, book several spots in one request, and apply promo codes and gift cards. Keys only do what you grant them, you can limit a browser key to your own websites, and a retried booking never books twice.
For: developers building a custom booking flow, a mobile app, or an integration on top of a studio's class schedule.
The engine behind our booking page, as a REST API.
If the booking page and the widget can't do what you need, the API can. It covers the whole flow, from showing which classes and courses have room to taking payment, plus gift cards, promo codes and customer records.
Public keys go in the browser. List your websites on a key and browsers on other sites are turned away. Secret keys stay on your server. Each key has its own scopes. Booking requests take an idempotency key, so a retry never double-books, and a class never sells more spots than it has.
When a booking embed stops being enough.
If you've built on a hosted page or a generic embed, you've probably hit some of these.
An iframe that never fits
It doesn't quite match your product or your design system, and never will.
No way into your app
Booking only works on the web, so your mobile app has to send people to a browser.
Copying data by hand
Exporting classes and customers from one system to another instead of reading them live.
Browser keys that work anywhere
Anyone can lift the key off your page and use it, with no limit on where or what.
The same spot sold twice
A retry or a refresh during checkout quietly books it a second time.
No real reference
You end up guessing at request shapes.
What you get to build with.
- REST endpoints for the whole flow. Class and course availability, bookings, gift cards, promo codes and customers.
- Public & secret keys. Public keys for the browser, which you can limit to the websites you list. Secret keys for your server.
- Per-key scopes. Give each key only the access it needs.
- Idempotency keys. Retry a booking request safely, and the same spot is never sold twice. You can also hold spots while a customer checks out.
- Signed webhooks. We tell your server about bookings, payments, refunds and waitlist offers as they happen, and sign each one so you can check it came from us.
- Rate limits. Read and validation endpoints are rate-limited.
- OpenAPI 3.1 spec. Download the full spec and generate typed clients from it.
Your own booking flow, start to finish.
Create your keys
Make a public key for the browser with your allowed origins, and a scoped secret key for your server.
Read upcoming events
Show what's coming up, and how many spots are left, in your own site or app.
Validate and book
Check any promo code or gift card, then send the booking with an idempotency key. The booking is made and the payment is taken.
Confirm and follow up
Customers get the usual confirmation and reminder emails, and the booking shows up in the admin and reports like any other.
Related features
Build the checkout you want.
Set up a booking page this afternoon. Move it onto your own website, or build on the API, whenever you like.
30-day free trial · Cancel anytime