Retrieve seller bookings

  • Bookings
  • Booking
  • 1 route
How can a seller retrieve the list of bookings they manage?

This scenario explains how to retrieve the list of bookings visible to a seller through a single search endpoint. It is useful to build a back-office list, apply business filters, and identify the next file to inspect in more detail.

The route returns commercial and operational indicators such as booking status, payment status, product, main attendee, seller email, and commission when available.

Overview

Use this scenario when a seller needs to retrieve the bookings they manage and narrow the result set with business filters such as booking status, payment status, product, main attendee last name, or creation and departure dates.

The objective is to obtain a paginated booking list that can feed a seller workspace, a monitoring dashboard, or a follow-up queue.

Prerequisites

  • Have a valid x-api-key.
  • Use an accept-language value returned by GET/v0/locales.
  • Use an access token if your integration context requires authenticated seller access.
  • Define the filters that matter for your use case, for example booking_status, payment_status, product_id, customer_id, or sort.

Functional notes

  • This scenario focuses on listing bookings, not on retrieving the full detail of one booking.
  • Pagination is available with page and limit.
  • Sorting is available on departure_date, creation_date, and expiration_date.
  • The response can include useful seller-facing information such as salesman_id, seller_email, commission, and the main attendee inside households.
1

List seller bookings

Mandatory

This route returns the list of bookings matching your sales filters.

Prerequisites

Add the relevant filters such as customer_id, booking_status, start_date, end_date, limit, or page.

Calling CURL

curl -X GET \
  -H "x-api-key: $API_KEY" \
  -H "accept-language: en-US" \
  "https://api.clubmed.com/v2/bookings?booking_status=OPTION&limit=20&page=1"

Example answer

[
  {
    "id": "booking-1",
    "status": "OPTION",
    "product_id": "product-1",
    "start_date": "2026-07-05",
    "end_date": "2026-07-12",
    "customer_id": "customer-1"
  }
]

info: The route may return 206 Partial Content when the result is paginated. Make sure your integration handles pagination metadata as well.

Response codes

  • 200 OK: the booking list is returned.
  • 206 Partial Content: the list is paginated.
  • 400 Bad Request: invalid parameters.
  • 401 Unauthorized: missing or invalid token.
  • 416 Range Not Satisfiable: invalid pagination range.
GET/v2/bookings
See more