Skip to content

Read a chat agent conversation

POST
/voice/chat-agent/history

READ-ONLY. A POST because voice takes the selector as a body.

In READ_ONLY_POST_ROUTES: left in this router’s billable bucket, a read-only key could not read its own chat history.

Authorizations

Parameters

Header Parameters

X-Target-Org-Id
Any of:
string

Request Body required

Which conversation to read.

object
key
additional properties
any

Responses

200

Successful Response

object
data
required

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
items
Array
key
additional properties
any
pagination
Any of:
object
has_next
required

Whether there are more pages

boolean
limit
required

Items per page

integer
next_cursor
Any of:
string
notes
Any of:
Array<string>
page
required

Current page number (1-indexed)

integer
total
required

Total number of items

integer
total_available
Any of:
integer
total_is_lower_bound
Any of:
boolean

422

Validation Error

object
detail
Array<object>
object
loc
required
Array
msg
required
string
type
required
string