Skip to main content
The MarketBox API’s large lists use cursor-based pagination. There are no page numbers — you ask for a page of results, and the response tells you whether more exist. A few small or windowed lists return everything in one response, with no cursor and no nextCursor: locations and skills (Locations and skills), and the supplier plane’s lists — bookings in a window, schedules, blocked times, travel zones and venues (Supplier portal: bookings and Supplier portal: availability). Each endpoint’s reference says which kind it is. The catalog lists — GET .../services and, under a service, its offerings, packages and business models — also return everything in one response. They take no limit or cursor, but their body still carries nextCursor, and it is always null. Code that follows the loop below works unchanged on them.

Query parameters

Both are optional. Omitting cursor returns the first page. Two lists use smaller limits: A page can hold fewer than limit items even when more remain. Never stop on a short page — only nextCursor: null means the end.

Response shape

  • data — the items on this page, in the endpoint’s natural ordering.
  • nextCursor — the token for the next page, or null if there are no more results.

Iterating in code

Rules

  • Opaque cursors. A cursor is a base64-encoded blob with internal structure. Treat it as a magic token — never parse, decode, or construct one yourself. Its format may change without notice.
  • Cursors are tied to a filter set. If you change the query params (status, startDate, etc.) between calls, the cursor’s behavior is undefined. Either keep filters identical across the iteration, or start a fresh iteration with no cursor.
  • nextCursor: null means done. Don’t loop again when the response says there are no more pages.
  • No total counts. The API does not return how many items remain. If you need a count, walk the full iteration.

Errors

  • 400 VALIDATION_ERROR — limit is non-numeric, or outside the list’s range. message names the field, for example limit: ….
  • 400 BAD_REQUEST with message "Invalid cursor" — cursor is malformed (not valid base64, not a cursor this API issued) or came from a different list. Start again without it.
  • 400 INVALID_CURSOR — the same failure on GET .../suppliers/me/alerts, which has its own code. See Supplier portal: insights and alerts.