Pagination

Understand how to iterate through large result sets using cursor-based pagination.

Pagination

List endpoints in the MeetRox API use cursor-based pagination, which provides stable and efficient traversal of large datasets — even when records are being added or updated between requests.


Parameters

ParameterTypeDescription
firstintegerNumber of records to return from the start of the result set. Default: 50, max: 100.
afterstringCursor marking the position after which to fetch records. Use the end_cursor from a previous response.
lastintegerNumber of records to return from the end of the result set.
beforestringCursor marking the position before which to fetch records. Use the start_cursor from a previous response.

Use first + after to paginate forward. Use last + before to paginate backward.


Response Metadata

Every list response includes a meta object:

{
  "meta": {
    "page_size": 50,
    "has_next_page": true,
    "has_previous_page": false,
    "start_cursor": "g2wAAAABaAJtAAAACGNhbGxfaWRhKm4=",
    "end_cursor": "g2wAAAABaAJtAAAACGNhbGxfaWRhMm4=",
    "errors": [],
    "params": {}
  }
}
FieldTypeDescription
page_sizeintegerNumber of records returned in this page
has_next_pagebooleanWhether there are more records after this page
has_previous_pagebooleanWhether there are records before this page
end_cursorstringPass as after to fetch the next page
start_cursorstringPass as before to fetch the previous page

Iterating Through All Records

To retrieve all records, fetch pages sequentially until has_next_page is false.

Example — First Page

curl "https://api.meetrox.ai/v1/calls?first=100" \
  -H "x-api-key: YOUR_API_KEY"

Example — Next Page

Take the end_cursor from the previous response and pass it as after:

curl "https://api.meetrox.ai/v1/calls?first=100&after=g2wAAAABaAJtAAAACGNhbGxfaWRhMm4=" \
  -H "x-api-key: YOUR_API_KEY"

Repeat until has_next_page is false.


Combining Pagination with Filters

Pagination and filters can be combined freely. The cursor preserves your filter context — you don't need to re-send filters on subsequent pages.

# First page: calls from the last 30 days, ordered by timestamp
curl "https://api.meetrox.ai/v1/calls?first=100&filters[0][field]=timestamp&filters[0][op]=>=&filters[0][value]=2026-04-20T00:00:00Z" \
  -H "x-api-key: YOUR_API_KEY"

# Next page
curl "https://api.meetrox.ai/v1/calls?first=100&after=<end_cursor>&filters[0][field]=timestamp&filters[0][op]=>=&filters[0][value]=2026-04-20T00:00:00Z" \
  -H "x-api-key: YOUR_API_KEY"

Notes

  • Cursors are opaque strings. Do not decode or construct them manually.
  • Cursors are tied to the order and filters of the original request. Changing the sort order or filters will invalidate existing cursors.
  • The default sort order is updated_at desc, id desc. See Calls for available sort fields.

Did this page help you?