Retrieve a trace
Retrieve a single trace by trace_unique_id, including aggregate metrics and the full span tree. Metadata keys beginning with _ are reserved for platform use and are omitted from customer-facing span and trace responses, so they do not round-trip through read APIs.
Authentication
Use your Respan API key for Respan API authentication. Enter only the Respan API key value; clients send Authorization: Bearer <RESPAN_API_KEY>. For /api/responses, provider credentials such as Perplexity, OpenAI, or Azure OpenAI go in Settings -> Providers or respan_params.credential_override in the request body, not in this authentication field.
Use a dashboard JWT only for dashboard-authenticated endpoints. Respan API-key endpoints use the respanApiKey auth field instead.
Path parameters
Response
Alias of unique_organization_id.
Number of LLM-call spans.
Root span input. API key responses may include full storage-enriched content.
Root span output. API key responses may include full storage-enriched content.
Customer metadata. Keys beginning with _ are reserved and omitted from customer-facing responses.
Workflow or trace-group identifier.
Primary/root model used.