List chat records
⚠️
Preview — this feature is being built; the design below is the spec.
GET https://app.syntic.ai/v1/compliance/chatsReturn the chat histories of members using Syntic’s own chat apps under the organization’s plan, newest first. These are records for review and eDiscovery; they are not a way to read or write chats on a person’s behalf.
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. |
Query parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
user_id | string | ||
starting_at | string | Updated at or after. | |
ending_at | string | ||
include_deleted | boolean | true | Include chats the person deleted. |
limit | integer | 20 | 1 to 100. |
after_id | string | Next page: the previous page’s last_id. | |
before_id | string | Previous page: the previous page’s first_id. |
Response
200 OK, Content-Type: application/json
{
"data": [
{
"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
}
],
"has_more": false,
"first_id": "chat_01JCV7V9X1Z3B5D7F9H1",
"last_id": "chat_01JCV7V9X1Z3B5D7F9H1"
}| 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. |
has_more | boolean | true when another page exists after this one. |
first_id | string or null | Pass as before_id to go back a page. |
last_id | string or null | Pass as after_id to get the next page. |
Examples
curl -sS "https://app.syntic.ai/v1/compliance/chats?user_id=user_01J9Y0A2C4E6G8J0L2N4&starting_at=2026-10-01T00:00:00Z" \
-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. |
| 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?