Pagination
List endpoints return a page of results with an opaque cursor. Ask for the next page with the cursor from the previous response.
Request
| Parameter | Description |
|---|---|
limit | How many items per page. |
after | The next_cursor from the previous page. Omit it for the first page. |
curl "https://api.hermeseus.com/v3/HAPI/activities/products?limit=20" \ -H "Authorization: Bearer $ACCESS_TOKEN"
Response
List responses carry the page in data, whether more remain in has_more, and the cursor for the next page in next_cursor.
{
"object": "activity_product_list",
"data": [ /* … */ ],
"has_more": true,
"next_cursor": "cur_Mg"
}To fetch the next page, pass that cursor as after:
https://api.hermeseus.com/v3/HAPI/activities/products?limit=20&after=cur_Mg
Cursors are opaque.
Treat
next_cursor as a token to pass back verbatim; do not build or parse it yourself. When has_more is false, next_cursor is null and you have reached the end.
Searches vs lists
Flight and hotel searches return the full result set in one response and are not paginated. Cursor pagination applies to list endpoints, such as the activities catalogue and your bookings.
Was this page helpful?