List execution traces
⚠️
Preview — this feature is being built; the design below is the spec.
GET https://app.syntic.ai/v1/agents/executions/{execution_id}/tracesReturn a run’s traces in step order, for runs too long to read in one response.
For how this fits into a full workflow, see Executions.
Headers
| Header | Required | Value |
|---|---|---|
Authorization | Yes | Bearer <key>: a private inference key (sk_live_...). See Authentication. |
syntic-beta | Yes, while in preview | agents-2026-11-01. Without it the call fails with 400 beta_required. See Versioning. |
Path parameters
| Parameter | Type | Description |
|---|---|---|
execution_id | string | The run id, starting with exec_. |
Query parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
after_step | integer | Return steps after this number. | |
limit | integer | 100 | 1 to 200. |
Response
200 OK, Content-Type: application/json
{
"data": [
{
"step": 200,
"step_type": "tool_call",
"label": "lookup_order",
"input": {
"order_id": "88123"
},
"output": {
"error": "order not found"
},
"error": "order not found",
"started_at": "2026-11-05T10:00:05Z",
"ended_at": "2026-11-05T10:00:06Z",
"duration_ms": 412,
"usage": null
}
],
"has_more": true,
"last_step": 399
}Examples
curl -sS "https://app.syntic.ai/v1/agents/executions/exec_01JC7N0Q8S2U4W6Y8A0C/traces?after_step=199&limit=200" \
-H "Authorization: Bearer $SYNTIC_API_KEY" \
-H "syntic-beta: agents-2026-11-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 | execution_not_found | No run with that id in this workspace. |
| 401 | authentication_error | invalid_api_key | The key is missing, unknown, revoked or expired. |
| 429 | rate_limit_error | rate_limited | Too many requests; wait for Retry-After. See Rate-limit headers. |
Related
Was this page helpful?