Skip to main content
GET
Get real-time chat history

Authorizations

Authorization
string
header
required

An API key from your Devic console, sent as Authorization: Bearer <key>. An embedded front end sends a tenant-session token instead, so no API key reaches the browser, and an OAuth integration sends its access token. Missing, invalid or expired credentials get a 401. See Authentication.

Path Parameters

identifier
string
required

The unique identifier of the assistant specialization

chatUid
string
required

The unique identifier of the chat conversation

Response

Real-time chat history retrieved successfully

chatUID
string
required
Example:

"550e8400-e29b-41d4-a716-446655440000"

clientUID
string
required
Example:

"client-123"

chatHistory
object[]
required
status
enum<string>
required
Available options:
processing,
completed,
error,
handed_off,
buffering,
waiting_for_tool_response,
limit_exceeded
Example:

"processing"

lastUpdatedAt
number
required
Example:

1706000000000

queuedMessages
number
Example:

0

pendingUserMessages
object[]
pendingToolCalls
object[]

Pending tool calls awaiting client-side execution

handedOffSubThreadId
string

Subagent thread ID (when status is handed_off)

Example:

"64f5a5b8c123456789abcdef"

stopReason
string

System stop reason (e.g. max_chat_messages_reached, error)

Example:

"max_chat_messages_reached"

recalledMemories
string[]

Memory-recall events of the in-flight run (source, query, facts/entities surfaced)

limitExceeded
object

Usage-limit details (when status is limit_exceeded)