Pagination

This API does not paginate list responses

Every list endpoint in openapi.json returns a plain JSON array — there is no count / next / previous envelope, and no page or page_size query parameters:

Endpoint	Returns
GET /v1/third-party/menu/	Array of ThirdPartyDish
GET /v1/third-party/orders/	Array of OrderResponse
GET /v1/third-party/hotels/rooms/	Array of RoomType
GET /v1/third-party/hotels/reservations/	Array of ReservationResponse
GET /v1/third-party/credentials/	Array of IntegrationCredential (owner-only)

[
  { "...": "first item" },
  { "...": "second item" }
]

Your integration should read the full array from a single response rather than expecting or requesting additional pages.

Limits

Sourced from the backend implementation, not yet in the spec

Confirmed from the view implementations, not from openapi.json.

GET /v1/third-party/menu/, GET /v1/third-party/orders/, and GET /v1/third-party/hotels/rooms/ and /reservations/ currently have no maximum result size — they return every matching row for the tenant in one response. For a tenant with a very large menu or a long order/reservation history, this can be a large payload. Plan your integration accordingly (for example, cache the menu rather than re-fetching it on every request) rather than assuming a small, bounded response.

This is different from the Channel Manager API, whose equivalent reservations endpoint is capped at 200 results.