The chat record object
⚠️
Preview — this feature is being built; the design below is the spec.
The chat_record object as the API returns it. Every field below appears in every response that returns this object; fields with no value are null rather than missing.
Example
{
"id": "chat_01JCV7V9X1Z3B5D7F9H1",
"type": "chat_record",
"user_id": "user_01J9Y0A2C4E6G8J0L2N4",
"title": "Q3 supplier contract review",
"product": "chat",
"model": "Amara S1.2",
"message_count": 14,
"file_count": 2,
"project_id": null,
"created_at": "2026-10-14T09:00:00Z",
"updated_at": "2026-10-14T09:42:00Z",
"deleted_by_user_at": null,
"messages": [
{
"role": "user",
"created_at": "2026-10-14T09:00:00Z",
"content": [
{
"type": "text",
"text": "Summarise the termination clauses in the attached contract."
},
{
"type": "file",
"file_id": "cfile_01JCV8W0Y2A4C6E8G0J2"
}
]
},
{
"role": "assistant",
"created_at": "2026-10-14T09:00:20Z",
"content": [
{
"type": "text",
"text": "There are three termination clauses: 11.2 (for convenience, 90 days' notice)…"
}
]
}
]
}Fields
| Field | Type | Description |
|---|---|---|
id | string | Unique id of this object. |
type | string | The object type, always chat_record. |
user_id | string | The member concerned. |
title | string | Display title. |
product | string | chat (web and desktop) or mobile. |
model | string | Model id. |
message_count | integer | See the endpoint pages below. |
file_count | integer | See the endpoint pages below. |
project_id | string or null | See the endpoint pages below. |
created_at | string | When it was created, RFC 3339 UTC (some older objects use Unix seconds). |
updated_at | string | When it last changed. |
deleted_by_user_at | string or null | Set if the person deleted the chat. Records stay available here for the organization’s retention period unless a legal hold keeps them longer. |
messages | array | Messages with role, created_at and content blocks. |
Returned by
Was this page helpful?