Sign in
Eval runs

Get an iteration trace

Full trace envelope for one iteration: conversation messages, expected-vs-actual tool call analysis, and spans. The shape is rich and may evolve — treat it as an open document. Returns 404 with details.reason: "TRACE_NOT_AVAILABLE" when the iteration finished without a stored trace.

get/projects/{projectId}/eval-runs/{runId}/iterations/{iterationId}/trace

Path parameters

projectIdstring required

ID of the hosted project that contains the server.

runIdstring required

Eval run ID, as returned by POST /eval-runs.

iterationIdstring required

Iteration ID, as returned by the run's iterations list.

Response

The trace envelope.

object required

Trace document: messages, prompts (per-prompt expected/actual tool-call analysis), spans, and more.

Changes

Changed in 2 of the 81 revisions of this API.51

  • 8e393fd5825f5See the full diff
    • ●

      added the new CONFLICT enum value to the response property for the response status

      response-property-enum-value-added

    • ●

      added the new CONFLICT enum value to the response property for the response status

      response-property-enum-value-added

    • ●

      added the new CONFLICT enum value to the response property for the response status

      response-property-enum-value-added

    • ●

      added the new CONFLICT enum value to the response property for the response status

      response-property-enum-value-added

    • ●

      added the new CONFLICT enum value to the response property for the response status

      response-property-enum-value-added

  • ad9bf0de7ed41See the full diff
    • ○

      endpoint added

      endpoint-added