Pagination

List endpoints use cursor-based pagination. Pass the cursor from the previous response to fetch the next page.

# First page
curl "https://app.autorev.ai/api/v1/receptionists/RECEPTIONIST_ID/calls?limit=10" \
  -H "Authorization: Bearer ar_live_..."

# Next page (use cursor from previous response)
curl "https://app.autorev.ai/api/v1/receptionists/RECEPTIONIST_ID/calls?limit=10&cursor=eyJjcmVhdGVkX2F0Ijo..." \
  -H "Authorization: Bearer ar_live_..."

A paginated response looks like:

{
  "data": [
    { "id": "uuid", "direction": "inbound", "status": "completed" }
  ],
  "has_more": true,
  "cursor": "eyJjcmVhdGVkX2F0Ijo..."
}

When has_more is false, you have reached the last page.

Parameters and defaults

Parameter	Meaning	Default	Max
limit	Results per page	20	100
cursor	Opaque pagination cursor from the previous response	none (first page)	n/a

These defaults apply to the core list endpoints such as call history (GET /api/v1/receptionists/:id/calls) and SMS history (GET /api/v1/receptionists/:id/sms). A few endpoints use tighter bounds; for example, lead search (GET /api/v1/leads/search) returns 1-50 leads with a default of 10. The per-endpoint bounds are documented in the API Reference.

Tips

• Treat cursor as opaque. Do not parse or construct it; always take it from the previous response.
• Stop iterating when has_more is false rather than when a page comes back empty.
• List endpoints also accept filters (for example direction, date_from, date_to on calls). Keep filters identical across pages of the same iteration.