List project traces
Lists execution traces across a project's apps, most recent first. Supports field filters on started_at (time) and status via query parameters of the form started_at:gte=<RFC3339> and status=<value>.
Authorization
personalAccessToken Personal Access Token of a Dynamiq user — the only credential accepted by the management API (api.*). Prefix dyn_pat_ (legacy uak_ tokens still authenticate). Send as Authorization: Bearer <token>.
In: header
Path Parameters
Project UUID.
Query Parameters
Only traces started at or after this RFC 3339 timestamp.
Only traces started at or before this RFC 3339 timestamp.
Filter by trace status.
Page number (1-based).
Number of items per page. Values below the minimum or above the maximum are clamped to the nearest bound.
Comma-separated sort fields. Prefix a field with - for descending order, e.g. sort=-started_at.
Response Body
application/json
application/json
application/json
curl -X GET "https://example.com/v1/projects/497f6eca-6276-4993-bfeb-53cbbbba6f08/traces"{
"data": [
{
"id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
"source_id": "ae50a35c-df42-4eff-ba26-f8bc28d2af81",
"started_at": "2019-08-24T14:15:22Z",
"ended_at": "2019-08-24T14:15:22Z",
"status": "succeeded",
"input": null,
"output": null,
"usage": null
}
],
"pagination": {
"page": 0,
"page_size": 0,
"page_count": 0,
"total_count": 0
}
}{
"error": {
"code": "unauthorized",
"message": "Unauthorized"
}
}{
"error": {
"code": "not_found",
"message": "Not Found"
}
}Ingest trace runs
Ingests a batch of workflow/flow/node trace runs, as produced by the Dynamiq Python SDK's `TracingCallbackHandler` / `DynamiqTracingClient`. The collector validates `id`, `name`, `type`, `trace_id`, `source_id`, `start_time`, `end_time`, and `status`; the remaining fields are stored as-is. SDK-emitted fields not listed in the schema (such as `session_id` and `tags`) are accepted and ignored by the collector.
Download project traces
Streams a project's execution traces as a downloadable JSON file (`Content-Disposition: attachment; filename="<project_id>-traces.json"`). The body is a JSON array of trace objects — each with `id`, `started_at`, `ended_at`, `status`, `input`, `output`, and `usage` — ordered by `started_at` descending. When `include_runs` is `true`, each trace also carries a `runs` array. Optional time-range filters on `started_at` use the `started_at:gt|gte|lt|lte=<RFC3339>` form; `gt`/`gte` and `lt`/`lte` are mutually exclusive.