Skip to main content
The /bookings endpoint returns your bookings newest-first by default, with optional filters for status, scheduled date range and sort direction. Each record contains the full booking object (booker, service, location, payment state and more) so you rarely need follow-up lookups. All filters are optional and can be combined.

Endpoint

Required scope: bookings.read

Example request

Query parameters

string
Filter to bookings in a specific state. Accepted values: pending, accepted, declined, cancelled. Omit to return bookings of all statuses.
date-time
Return only bookings with a scheduled_at at or after this moment. Provide an ISO 8601 date-time value (e.g. 2026-08-01T00:00:00Z).
date-time
Return only bookings with a scheduled_at at or before this moment. Must not precede from when both are supplied.
string
Sort direction on scheduled_at. Accepted values: asc, desc. Defaults to desc (newest first).
integer
Number of results per page. Between 1 and 100. Defaults to 25.
integer
Page number to return, starting at 1. Defaults to 1.

Response schema

array
Ordered array of Booking objects matching your filters.
Pagination links for navigating the full result set.
object
Pagination metadata for the current response.

Example response

Combine status=accepted, a from timestamp and order=asc to walk your upcoming confirmed schedule in chronological order. Ideal for syncing bookings to a calendar or a “what’s next” dashboard widget.

Errors