Developers · Start here
Overview
What you can build on Bookare, and which part of the API to use.
Bookare has a complete REST API. Anything the Bookare screens do, your own code can do: run a venue from your systems, or build a booking website or app of your own on top of Bookare (“headless”), with Bookare keeping the timetable, availability, rules, payments and emails.
The three parts
| Part | Paths | For | Auth |
|---|---|---|---|
| Public | /public/... |
A website or app showing what the venue offers and taking guest bookings | none |
| Customer | /auth/..., /me/... |
A customer signed in to your app: their bookings, packs, payments | customer token |
| Admin | /admin/... |
Your back office: members, timetable, packs, sales, stays, imports | API key |
Every venue has its own API at its own address:
https://<venue>.bookare.app/api/v1
https://book.yourgym.com/api/v1 (if the venue uses its own domain)
What people build
- A gym’s own website with the live timetable, member sign-in, booking and pack purchase: guide.
- A salon’s or restaurant’s booking flow inside their site or app: guide.
- A hotel booking engine on the hotel’s own site: guide.
- Integrations: sync members to a CRM, daily reports, accounting exports, automations: guide.
- Migrations from another booking system: guide.
- No code at all: the booking widget is one line of HTML.
- AI: the same operations are available to AI assistants through MCP: MCP for developers, and to AI agents that set venues up for owners: AI agents.
Kinds of venue
What exists depends on how the venue takes bookings (booking_mode in GET /public/venue): classes (gyms and studios),
appointments (salons, trainers, tutors), tables (restaurants, bars) or stays (hotels, rooms, campsites, homes). A studio can
take classes and appointments. Endpoints that do not apply to a venue answer 404 not_found.
Where to go next
- Quickstart: your first calls in five minutes.
- API keys and customer tokens.
- Errors, dates, languages and limits.
- The reference: Public, Customer, Admin, or the OpenAPI description for Postman and SDK generators.