Skip to main content
GET
cURL

Authorizations

Authorization
string
header
required

Timbal API key. Obtain your API key from the Timbal platform settings. See Authentication for more information.

Path Parameters

org_id
string
required
project_id
string
required
env_id
string
required

Query Parameters

component_id
string | null

Filter to a single workforce component by its numeric app id (the value the SDK reads from TIMBAL_APP_ID, also returned as component.id on each run). Combines with component_uid: when both are set, rows must match both.

component_uid
string | null

Filter to a single workforce component by its manifest uid (the _id field in timbal.yaml, also returned as component.uid on each run). Display name is deliberately not accepted as a filter — it's user-editable and not guaranteed unique within a project.

trigger
string | null

Optional trigger filter. Accepts:

  • latest — runs from the env's most recent deploy batch.
  • a UUID — runs from that deploy batch.
trigger_type
string | null

Filter by what started the run: deploy (gate), manual (POST .../evals/runs), or push (deploy_config.evals_on_push CI runs). Orthogonal to trigger (a deploy-batch selector).

status
string | null

Filter by run status: running, passed, failed, or error.

include_logs
boolean

Include the captured CLI stdout/stderr in each run. Off by default — logs can be hundreds of KB per run.

include_results
boolean

Include the structured per-eval results document in each run. Off by default for the same size reason as include_logs; the single-run GET always returns it.

limit
integer<int64> | null

Max rows returned, newest first. Defaults to 50, capped at 200.

Response

Eval runs listed successfully

eval_runs
object[]
required