Get started

Pagination

How list endpoints page their results.

Lists that can grow without bound are paged with two query parameters.

curl "https://api.sevennadi.si/v2/agent/123e4567-e89b-12d3-a456-426655440000/executions?from=2026-10-01T00:00:00Z&to=2026-10-31T23:59:59Z&page_number=2&page_size=50" \
  -H "Authorization: Bearer vk-0123456789abcdef0123456789abcdef"

A paged response wraps the rows:

{
  "page_number": 2,
  "page_size": 50,
  "total": 131,
  "has_more": true,
  "data": []
}

• total is the number of rows that match the filters, across all pages.
• has_more is true while page_number × page_size is less than total.
• Rows are ordered newest first.

To read everything, request pages until has_more is false.

Things to know

• Paging is by offset. If rows are created while you page, a row can appear on two pages or be skipped. For an exact export, filter by a time range that has ended.
• A value outside the range is a 400, not a silent clamp.
• Not every list is paged. Short lists (agents, phone numbers, knowledge bases, providers, sub-accounts) return a plain array. Some extension lists use their own parameters, for example limit. Each reference page says which form its lists take.
• Some lists accept filters (status, dates, call type, batch). They are listed with each operation, for example in Executions.