Pagination
Most list endpoints aren’t paginated
Section titled “Most list endpoints aren’t paginated”Most list endpoints return all matching records in a single JSON array. There’s no page, page_size, count, next, or previous, and no query parameters for paging.
| Endpoint | Returns | Order |
|---|---|---|
GET /v1/restro/dishes/ |
Every active dish (ThirdPartyDish) |
By name |
GET /v1/restro/orders/ |
Every order placed with your credential (OrderResponse) |
Newest first |
GET /v1/hotels/bookings/ |
Every reservation placed with your credential (ReservationResponse) |
Newest first |
[ { "...": "first item" }, { "...": "second item" }]Exception: room types are paginated
Section titled “Exception: room types are paginated”GET /v1/hotels/roomtypes/ is the one exception on this API — it returns a DRF-style paginated envelope instead of a bare array:
{ "count": 1, "results": [ { "...": "first room type" } ]}Read results for the room types themselves; count is the total number of active room types for the tenant.
What this means for your integration
Section titled “What this means for your integration”- For the unpaginated endpoints, one request gets you the full list, so you don’t need a paging loop. If you only need one order or reservation, fetch it directly with
GET /v1/restro/orders/{external_order_id}/orGET /v1/hotels/bookings/{external_reservation_id}/. - For
GET /v1/hotels/roomtypes/, read fromresults, not the top-level response.
