Pagination - Talqing

Every list endpoint returns the same Page envelope and pages with limit and offset query parameters.

{
  "items": [],
  "has_more": false,
  "limit": 50,
  "offset": 0
}

Field	Type	Meaning
`items`	array	This page. Empty, never `null`.
`has_more`	boolean	Another row exists past this page.
`limit`	integer	The page size applied: yours, or the endpoint’s default.
`offset`	integer	The offset applied.

curl "https://api.talqing.com/v1/calls?limit=50&offset=100" \
  -H "Authorization: Bearer $TALQING_API_KEY"

No total, no cursor

There is no total count and no parameter that asks for one; walk to has_more: false to count. offset is the only way forward. Most lists are newest first (agents by last edit, calls by start), so rows created while you page shift later rows and a long walk can repeat or skip one. To page a busy list stably, close the window: GET /v1/calls takes start and end (default: the last 30 days up to now). Conversation and chat items default to oldest first (order=asc); order=desc returns the newest window, still chronological within the page.

Page size

limit above the endpoint’s maximum is a 422, not a clamp.

Default	Max	Endpoints
200	200	`GET /v1/agents`, `/v1/tools`, `/v1/tasks`, `/v1/faqs`, `/v1/calls`, `/v1/secrets`, `/v1/webhooks`, `/v1/integrations`, `/v1/integrations/catalog`, `/v1/integrations/{integration_id}/triggers`, `/v1/telephony/accounts`, `/v1/telephony/accounts/{account_id}/remote-numbers`, `/v1/telephony/phone-numbers`, `/v1/telephony/providers`, `/v1/streams`, `/v1/billing/credits/ledger`
200	500	`GET /v1/conversations/{conversation_id}/items`, `/v1/chats/{chat_id}/items`
100	200	`GET /v1/chats`, `/v1/conversations`, `/v1/conversations/{conversation_id}/sessions`, `/v1/calls/batches/{batch_id}/recipients`
50	200	`GET /v1/calls/batches`, `/v1/task-runs`, `/v1/webhooks/{webhook_id}/deliveries`, `/v1/email/batches`, `/v1/email/batches/{batch_id}/recipients`, `/v1/email/batches/{batch_id}/sends`, `/v1/whatsapp/batches`, `/v1/whatsapp/batches/{batch_id}/recipients`

Walking every page

Each SDK has one paginate helper for every Page endpoint. Its limit (default 200) is the page size it requests, not a cap on items yielded; it stops at has_more: false.

import { paginate } from "@talqing/sdk";

for await (const call of paginate((query) =>
  talqing.calls.list({ ...query, agent_id: agentId, type: "SIP_INBOUND" }),
)) {
  console.log(call.id, call.close_reason);
}

from talqing import paginate

for call in paginate(talqing.calls.list, agent_id=agent_id, type="SIP_INBOUND"):
    print(call["id"], call["close_reason"])

TypeScript takes paginate(fn, { limit: 50 }); Python takes paginate(fn, limit=50, **filters), and paginate_async with async for on AsyncTalqing.

Endpoints that do not use `Page`

Endpoint	Paging	Response
`GET /v1/catalog/voices`	`page` (0-based)	`voices`, `has_more`, `page`, `total_count` (nullable), plus filter facets
`GET /v1/catalog/avatars`	`offset`, `limit` (default and max 100)	`avatars`, `has_more`, plus filter facets
`GET /v1/catalog/models`	`cursor`, `limit` (default 20, max 50)	`models`, `next_cursor`

Walk these by hand; paginate does not apply. Other collection endpoints (GET /v1/catalog, GET /v1/email/senders, GET /v1/integrations/{integration_id}/mcp-tools, GET /v1/observability) return everything in one response.

​No total, no cursor

​Page size

​Walking every page

​Endpoints that do not use Page

No total, no cursor

Page size

Walking every page

Endpoints that do not use `Page`