List Syntic Code sessions
⚠️
Preview — this feature is being built; the design below is the spec.
GET https://app.syntic.ai/v1/compliance/code_sessionsReturn Syntic Code sessions run by members: who, which repository and branch, how much was changed. Transcripts are kept only when the organization turned on transcript retention.
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 | ||
repository | string | Host and path, for example git.example.com/acme/billing-service. | |
starting_at | string | ||
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": "csess_01JCY0Y2A4C6E8G0J2L4",
"type": "code_session_record",
"user_id": "user_01J9Y0A2C4E6G8J0L2N4",
"client": "syntic-code-cli 1.8.0",
"repository": "git.example.com/acme/billing-service",
"branch": "fix/rounding",
"model": "Syntic Code",
"turns": 31,
"tool_calls": 88,
"files_changed": 7,
"started_at": "2026-11-04T13:00:00Z",
"ended_at": "2026-11-04T14:12:00Z",
"transcript_available": true
}
],
"has_more": false,
"first_id": "csess_01JCY0Y2A4C6E8G0J2L4",
"last_id": "csess_01JCY0Y2A4C6E8G0J2L4"
}| Field | Type | Description |
|---|---|---|
transcript_available | boolean | false when transcripts are not retained or already expired. |
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/code_sessions?repository=git.example.com%2Facme%2Fbilling-service" \
-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?