assistant
GET /v1/assistant/conversations
List your own assistant conversations.
Authentication
Send an API key as a bearer token. The key must carry the tickets.reply permission; a key without it is refused with 403, not 404.
Where your organisation id goes
This endpoint takes org_id as a query parameter. Leave it out and the call covers your whole tenancy subtree; send it to narrow the call to one organisation.
Your organisation id is on the API keys screen in your dashboard, beside the key itself. It is the same id in every call you make.
Try it
Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.
curl -X GET https://api.zinndigital.com/v1/assistant/conversations \
-H "Authorization: Bearer zdk_live_…"Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console
Details
⛔ **Your own**, not your organization's. RLS scopes rows to a tenant and has no opinion about which colleague wrote them; an agency thread that starts "my card keeps getting declined" is not something every member should read back, so this filters on the calling user as well. An API-key principal has no user and cannot use this surface at all. Requires `tickets.reply`.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
cursor (query) | string | No | Opaque cursor from a previous page's `page.next_cursor`. |
limit (query) | integer | No | Maximum items to return (page size). |
org_id (query) | Uuid | No | Narrow to one organization. ⛔ Narrows, never widens: the base set is always what you may act in, and an `org_id` you cannot act in intersects to nothing rather than raising — a… |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
data | AssistantConversation[] | Yes | — |
page | PageMeta | Yes | — |
Errors this endpoint can return
401 · 403 · 422 · 429