List agent conversations
Every chat a shopper has had with this store’s AI assistant, newest first. ONE LIST COVERS THE WHOLE INBOX. The dashboard shows active by default, hides closed, and offers a third “all” mode; here that is ?status=, and omitting it returns everything. PAGED BY CREATION TIME, NOT BY updated_at, even though the dashboard sorts on updated_at. Every reply, takeover, assignment and status change rewrites that column, so a client walking the list while shoppers are chatting would skip conversations that jumped ahead of its position and repeat ones that fell behind it. created_at never moves. THE TRANSCRIPT IS NOT EMBEDDED. A conversation’s message count is unbounded, so an inline array would be a page with no cursor. Read /api/v1/agent-conversations//messages. external_id is deliberately not published. It is the shopper’s WhatsApp or Instagram handle, and you can already answer them through the messages route, which delivers on their channel AND records the reply in the merchant’s own transcript.
Authorizations
A secret API key. Publishable keys cannot reach this API. A key may carry an expiry, and an expired key is refused exactly like an unknown one, with a 401 that names no reason; check the key's expires_at in the dashboard rather than inferring it from a response. When a merchant rolls a key's secret they choose a grace window of up to 3 days, and for its duration BOTH the new secret and the one it replaced authenticate, so an integration moves over on its own deploy schedule instead of at the instant the button is pressed. Move before the window closes: after it, the old secret is refused. Nothing else about this contract moves with a roll. The key keeps its id and its scopes, so the only thing an integration updates is the credential itself.
Query Parameters
active is the merchant's working inbox, closed is the archive. Omit it for both, which the dashboard can only ask for as status=all. A value outside this set is a 400 rather than an ignored filter, because a closed conversation served as part of an unfiltered page reads as one still waiting on a reply.
active, closed human is the queue that matters operationally: the assistant has stopped answering those and a real person is waiting.
bot, human Where the shopper reached this store. It also decides where a reply is delivered.
website, whatsapp, instagram One teammate's conversations, by store user id. An EMPTY value is a 400 rather than "no filter": a client building the query from a variable it forgot to set would otherwise receive the whole inbox and read it as one person's workload. There is no way to ask for the unassigned ones here.
Rows per page. Out of range is a 400 rather than a silent clamp, so a client asking for more than 100 learns it did not get it.
1 <= x <= 100The next_cursor from the previous page. Opaque: decode nothing from it and construct nothing by hand, since its encoding is not part of this contract. Omit it to read the first page.
