Read the canonical metadata trace for a run
const url = 'https://api.katara.com/katara/v1/orgs/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/environments/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/runs/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/trace?limit=25';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url 'https://api.katara.com/katara/v1/orgs/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/environments/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/runs/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/trace?limit=25' \ --header 'Authorization: Bearer <token>'Requires synapse:runs:read and current run visibility, including key resource restrictions and environment reset. Returns canonical metadata only. Delivery records the last acknowledged trace projection, not engine availability or billing settlement. Current producers cover terminal runs, recorded inference outcomes, frozen policy decisions and managed tool outcomes. No private engine URL, project selector, prompt, response or claim credential is exposed.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Header Parameters
Section titled “Header Parameters”Optional for reads after sign-in. Use the UUID of the account that loaded the application. A different current cookie account returns account_changed before the handler runs. Session bearer and API key clients do not require this header.
Query Parameters
Section titled “Query Parameters”Responses
Section titled “Responses”Successful request
object
object
object
Exact scoped reservation/outcome record. Its presence does not imply a settled charge.
object
object
object
object
object
Example
{ "data": [ { "event": { "schema_version": 1, "mode": "test", "usage_class": "simulation", "kind": "run", "outcome": "completed", "reason": "none" }, "delivery": "pending" } ]}Account_changed: reload and review with the signed-in account.
default
Section titled “default”Request error
object
object
Stable; branch on it. Any operation can answer invalid_request, with param naming the refused field when there is one; human_session_required, when an API key, service account or workload calls an operation only a signed-in person may perform; reauthentication_required, when a person’s sign-in is too old for the operation; permission_denied; route_not_found and method_not_allowed, when no operation matches the path or method; and feature_unavailable, when the operation’s service is not enabled on this deployment.
The request field a refusal is about, such as the agent_id or run_id query parameter; null when the refusal is not about one field.
Example
{ "error": { "action": "sign_in" }}