The Bookablesites API provides programmatic access to your booking data so you can automate workflows, synchronize systems, and manage bookings, customers, services, employees, and locations. All endpoints require authentication; after obtaining a token, include it as a Bearer token in the Authorization header for subsequent requests.
Authentication
- POST /auth/token — request an access token.
- Use the returned token as: Authorization: Bearer <token> for all API calls.
Customer
- List all customers
- Retrieve a customer by ID
- Create, update, or delete a customer
- Use case: sync clients with your CRM or other tools
Coupon
- List coupons
- Create or remove coupons
- Use case: automate discounts and marketing promotions
Employees
- List, add, update, or delete employees
- Use case: keep employee data and schedules synchronized with internal HR systems
Locations
- List, create, update, or delete locations
- Use case: maintain consistent location data across platforms
Services
- List services and get service details
- Create, update, or delete services
- Use case: manage what clients can book from a central system
Appointments
- List all appointments
- Retrieve appointment details by ID
- Create or cancel appointments
- Use case: integrate booking flows, trigger external actions, or manage bookings programmatically
Bookings
- Endpoints supporting booking workflows and grouped bookings (depending on setup)
- Use case: implement custom booking logic or multi-seat reservations
Typical use cases:
- Automatically add new customers to your CRM when they book via Bookablesites.
- Create and apply discount coupons during campaigns.
- Sync employee schedules from an internal HR tool.
- Update services and prices centrally and push changes to the booking system.
- Display available appointment slots on a custom website or mobile app.
- Cancel or reschedule appointments from an external platform.
- Pull booking data for custom reports or dashboards.
- Build custom workflows using webhooks and API triggers.
Note:
- All requests require proper authentication.
- The API follows RESTful conventions for resource paths and HTTP methods.
- Consult the official API documentation for exact endpoint URLs, request/response formats, rate limits, and error handling details.
