Dynamiq
Tracing

List service traces

Lists execution traces of a deployed service, most recent first (ordered by started_at descending).

GET
/v1/services/{service_id}/traces

Authorization

personalAccessToken
AuthorizationBearer <token>

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

service_id*string

Service UUID.

Query Parameters

page?integer

Page number (1-based).

page_size?integer

Number of items per page. Values below the minimum or above the maximum are clamped to the nearest bound.

sort?string

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/services/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"
  }
}

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.

Get a trace with runs

Returns a single trace together with its full run tree. The trace carries `started_at`/`ended_at` while each run carries `start_time`/`end_time` — this mirrors the server responses and is intentional.