Skip to main content

Limiting Results

List endpoints accept a limit query parameter. The default and maximum vary by endpoint. The API does not provide page, offset, or cursor parameters, and does not return a continuation token for fetching the next page.

Response Shape

List endpoints return an array of resources together with a count field.

Response Fields

count is the count in this response, not a tenant-wide total.

Filters

Some list endpoints accept filter parameters.

GET /api/v1/sessions

GET /api/v1/knowledge

About assigneeType and type filtersassigneeType (sessions) and type (knowledge) are applied in memory after the first limit rows are read from DynamoDB. When either filter is set, count in the response reflects matches within those first limit rows only — not the tenant-wide total.For exhaustive enumeration, omit these filters and filter on the client side.

Examples

cURL

JavaScript

Best Practices

  1. Do not request more than you need with limit — larger responses take longer to fetch and parse.
  2. When using assigneeType or type filters, remember count is partial. If you need a complete enumeration, fetch without the filter and filter client-side.
  3. Keep concurrency below ~20 RPS per API key to avoid pressuring upstream DynamoDB capacity.
Last modified on May 18, 2026