Sign in
Eval runs

Get an iteration's step results

One row per authored test step, in order, with status (ok/fail/skipped/pending), a reason, and any evidence (screenshots, replay-video offset, widget tool calls). The fastest way to see which step failed and why. Unlike /trace, a missing trace is not a 404 — step verdicts still return, just without evidence.

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

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 ordered step results as a page envelope.

nextCursorstring

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

  • f311b5e012641See the full diff
    • ○

      endpoint added

      endpoint-added