Skip to main content
The GET /booking/ endpoint returns your bookings wrapped in the standard response envelope. Use query parameters to narrow results with filters, control the ordering, and page through large result sets. All requests require a bearer token:

Filter

Combine filter parameters to return only the bookings you need. Available filters include status, teamId, eventTypeIds, attendeeEmail, attendeeName, and bookingUid, plus date-range filters for start, creation, and update times: afterStartDate, beforeEndDate, afterCreatedDate, beforeCreatedDate, afterUpdatedDate, and beforeUpdatedDate. The example below returns upcoming bookings for a specific attendee that start within a date range. GET /booking/ has no accepted bucket — the valid values are upcoming, past, cancelled, unconfirmed, and recurring:

Sort

Order results with sortStart, sortEnd, sortCreated, or sortUpdated. Each accepts asc or desc. This request lists the most recently created bookings first:

Paginate

Use page and limit to page through results. page selects the page number and limit sets the number of bookings per page:
Every response includes a meta.pagination object describing the current page and total result set:
To retrieve all bookings, request page=1, then keep incrementing page and refetching until page === totalPages. Once the current page equals totalPages, you have reached the last page and can stop.
This loop does not return every booking. GET /booking/ defaults to status=upcoming and there is no all value, so a caller who omits status pages cleanly to the end of a set that excludes everything already in the past. To sweep the whole history, run the loop once per bucket: upcoming, past, cancelled, unconfirmed, recurring.

Reference

For the complete list of parameters and response fields, see the full List bookings endpoint.