Get a chat record
⚠️
Preview — this feature is being built; the design below is the spec.
GET https://app.syntic.ai/v1/compliance/chats/{chat_id}Return one chat with every message in order, including tool calls and the ids of attached files.
For how this fits into a full workflow, see Compliance API.
Headers
| Header | Required | Value |
|---|---|---|
Authorization | Yes | Bearer <admin key>: an Admin API key (sk_admin_...) that carries the compliance:read scope (plus compliance:write for deletions and holds). Enterprise plans only. See Compliance API. |
syntic-beta | Yes, while in preview | compliance-2026-12-01. Without it the call fails with 400 beta_required. See Versioning. |
Path parameters
| Parameter | Type | Description |
|---|---|---|
chat_id | string | Starts with chat_. |
Response
200 OK, Content-Type: application/json
{
"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)…"
}
]
}
]
}| Field | Type | Description |
|---|---|---|
product | string | chat (web and desktop) or mobile. |
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. |
Examples
curl -sS "https://app.syntic.ai/v1/compliance/chats/chat_01JCV7V9X1Z3B5D7F9H1" \
-H "Authorization: Bearer $SYNTIC_ADMIN_KEY" \
-H "syntic-beta: compliance-2026-12-01"Errors
Errors use the error envelope and carry a request_id. Codes specific to this operation:
| Status | type | code | When |
|---|---|---|---|
| 400 | invalid_request_error | beta_required | The syntic-beta header is missing. |
| 404 | not_found_error | chat_not_found | No chat record with this id. |
| 401 | authentication_error | invalid_api_key | The admin key is missing, unknown, revoked or expired. |
| 403 | permission_error | admin_key_required | An inference key was used. |
| 403 | permission_error | scope_missing | The admin key lacks the compliance:read (or, for writes, compliance:write) scope. |
| 429 | rate_limit_error | rate_limited | Too many requests; wait for Retry-After. See Rate-limit headers. |
Was this page helpful?