Skip to content

DevelopersEssentials

Pagination

Every list endpoint returns one page at a time, with a cursor that points at the next page. Most lists are newest first; appointments are in calendar order, soonest first. Cursors don't skip or repeat items when new ones arrive while you're paging.

On this page

Parameters and response

limit
How many items to return, from 1 to 100. Defaults to 25.
cursor
Where to continue: the next_cursor of the previous page, passed back unchanged.
A list response
{
  "data": [
    { "id": "3f6c2a9e-…", "started_at": "2026-10-24T15:41:07Z", "summary": "…" },
    { "id": "9b1d7e40-…", "started_at": "2026-10-24T13:02:55Z", "summary": "…" }
  ],
  "has_more": true,
  "next_cursor": "WyIyMDI2LTEwLTI0VDEzOjAyOjU1LjAwMDAwMFoiLCI5YjFkN2U0MC0uLi4iXQ"
}
data
The items on this page.
has_more
Whether there are more items after this page.
next_cursor
Pass it as cursor to get the next page. null on the last page.

Reading every page

Keep the same filters on every request and change only cursor. Stop when has_more is false.

# first page
curl "https://api.assistcall.ai/v1/calls?limit=100&started_after=2026-10-01T00:00:00Z" \
  -H "Authorization: Bearer $ASSISTCALL_TOKEN"

# next page: same filters, plus the cursor from the last response
curl "https://api.assistcall.ai/v1/calls?limit=100&started_after=2026-10-01T00:00:00Z&cursor=WyIyMDI2LTEwLTI0VDE..." \
  -H "Authorization: Bearer $ASSISTCALL_TOKEN"

Filters

Lists take their own filters next to limit and cursor, for example started_after and started_before on calls, or status=open on messages. Each endpoint's filters are in the API reference. Unknown parameters are refused (400 unknown_parameter) rather than ignored, so a typo can't silently return everything.

About cursors

Treat a cursor as an opaque string: don't build or change one, or you'll get 400 invalid_cursor. Cursors don't expire, but they belong to the list and filters they came from.

To sync new items regularly, remember the newest timestamp you've seen and use it as the next run's started_after (or the equivalent filter), rather than paging through everything again. Better still, let webhooks tell you when something new happens.

Try "token", "webhook signature", "rate limit" or "custom domain".