Get an activity
⚠️
Preview — this feature is being built; the design below is the spec.
GET https://app.syntic.ai/v1/compliance/activities/{activity_id}Return one activity record.
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 |
|---|---|---|
activity_id | string | Starts with act_. |
Response
200 OK, Content-Type: application/json
{
"id": "act_01JCR4S6U8W0Y2A4C6E8",
"type": "activity",
"product": "chat",
"action": "chat.message_sent",
"actor": {
"type": "user",
"id": "user_01J9Y0A2C4E6G8J0L2N4",
"email": "dana@example.com"
},
"resource": {
"type": "chat",
"id": "chat_01JCV7V9X1Z3B5D7F9H1"
},
"ip": "203.0.113.24",
"user_agent": "Syntic Desktop 2.4.1 (macOS 15.1)",
"occurred_at": "2026-11-05T10:00:00Z"
}| Field | Type | Description |
|---|---|---|
product | string | api, console, chat, code, agents or admin. |
action | string | A dotted name such as chat.file_uploaded, code.session_started or api_key.created. The full list is on the Compliance API page. |
actor | object | Member, service account or syntic. |
resource | object | What was acted on. |
Examples
curl -sS "https://app.syntic.ai/v1/compliance/activities/act_01JCR4S6U8W0Y2A4C6E8" \
-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 | activity_not_found | No activity 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?