Search web-chat conversations
POST /voice/chats/search
READ-ONLY. A POST because the filter set is too wide for a query string.
The ORGANISATION’s view of its web-chat conversations. Voice’s own model
accepts either a user_id or an org_id; the org is pinned from the key
here, so a caller always gets their own conversations and user_id can
only narrow within them.
Tiered read by an explicit READ_ONLY_POST_ROUTES entry - see
/voice/call-results/search for the same reasoning.
Authorizations
Parameters
Header Parameters
Request Body
Filters: limit (max 200), offset, ids, search (chat name), updated_after, updated_before, sort_by, sort_order, and user_id to narrow to one visitor.
object
Responses
200
Successful Response
object
A LIST result from voice, normalised so items is always present.
Voice is inconsistent about whether a list comes back bare or under a named
key (collections, files, routes, chats, …). Both are preserved:
the original key is kept for anyone reading voice’s docs, and items
always holds the same rows so a client can page one way.
object
object
Whether there are more pages
Items per page
Current page number (1-indexed)
Total number of items
422
Validation Error