Pagination
Offset pagination (limit_count / limit_offset), as published on developer.ringover.com
List endpoints support offset-based pagination with two query parameters:
| Parameter | Description | Default |
|---|---|---|
limit_count | Maximum number of items to return | 100 (max varies by endpoint) |
limit_offset | Number of items to skip | 0 |
curl --header "Authorization: your-api-key-here" \
"https://public-api.ringover.com/v2/calls?limit_count=50&limit_offset=0"Providing limit_offset X with limit_count Y skips the first X results and returns the following Y.
Applies to (per the official docs): calls, contacts, conversations, messages, blacklists, snooze logs, and other list endpoints — check the specific operation in the API Reference for its exact default/max.
Cursor variant on some call endpoints
Some call-related endpoints also support cursor-based pagination via last_id_returned, described as an alternative « to avoid duplicates » compared to limit_offset. Use whichever the specific operation documents.
Deprecated pagination params
A few older endpoints (e.g. contacts) still document a deprecated pagination + alphabetical_order character-based scheme. Prefer limit_count / limit_offset for new integrations.