List conversations
One page of conversations.
- Authentication
- Bearer token
- Retries
- Safe to repeat
- Body
- None
- Version
- 2026-09-03
cursor is the mode to use for anything that walks the whole list - exports, infinite scroll, an integration syncing conversations. It is constant-cost at any depth and stable while new conversations arrive; page is neither, and exists because a numbered pager needs it.
search_transcript=true widens q from metadata - visitor, page, contact details, title - to what was actually said, using the full-text index that has been in the schema since the first migration and, until now, was referenced by no query in the codebase.
count=false skips the COUNT(*), which is the half of the request that scans. total comes back as -1 and has_more is the field to read.
outcome, sentiment, intent, min_rating / max_rating, min_lead_score and the date bounds are what make the insight panels lead somewhere. Before them, the dashboard could tell a customer that 22% of their pricing conversations were refused and offer no way to open those twelve conversations - which is a report, not a tool.
Path parameters#
Query parameters#
Responses#
Errors#
Failures use one envelope on every endpoint, described in Retries, versioning and limits. The codes you are most likely to meet here:
validation_error· 422 — The payload was well-formed JSON but failed schema validation.unauthenticated· 401 — The request carried no API key, or one the API could not verify.forbidden· 403 — The key is valid, but it is not allowed to do this — either the scope is missing or the resource belongs to another workspace.rate_limited· 429 — Too many requests in the current window. The limit is per workspace, and some endpoints add a per-agent limit on top.
More Dashboard endpoints#
Something unclear or missing? Tell us and we’ll fix it.