Inspect a trace

:::callout amber Not available yet. The management API is documented ahead of its implementation — the request and response shapes below are a stable contract we're committing to, but calling these endpoints today returns 404. Manage traces in the dashboard in the meantime. The live gateway endpoints today are POST /v1/chat/completions, POST /v1/embeddings and GET /v1/models. :::

A lightweight HEAD request that returns metadata about a trace as response headers, without transferring the trace body. Useful for checking whether a payload archive exists before you fetch it.

HEAD /v1/traces/{request_id} Coming soon

https://api.routeur.ai

Path parameters

request_id string required

Trace request id, e.g. 01K.... Returned from the routeur block of any chat response.

Response headers

X-Routeur-Trace-Status integer optional

Caller-visible HTTP status the original request received.

X-Routeur-Trace-Provider string optional

Final upstream provider used.

X-Routeur-Trace-Payload url optional

Signed URL for the payload archive if one exists. Absent when payload storage is disabled.

Returns

An empty body. Status is 200 when the trace exists, 404 otherwise.

← Retrieve trace List API keys →

const res = await fetch( `https://api.routeur.ai/v1/traces/${requestId}`, { method: "HEAD", headers: { Authorization: `Bearer ${process.env.ROUTEUR_KEY}` } } ); const payloadUrl = res.headers.get("X-Routeur-Trace-Payload");

r = requests.head( f"https://api.routeur.ai/v1/traces/{request_id}", headers={"Authorization": f"Bearer {os.environ['ROUTEUR_KEY']}"}, ) payload_url = r.headers.get("X-Routeur-Trace-Payload")