Create Eval Job
Enqueue a background eval job (today: generate_initial — Claude-generate an initial eval suite for a workforce component, written to the env branch’s worktree).
Authorizations
Timbal API key. Obtain your API key from the Timbal platform settings. See Authentication for more information.
Body
Commit the generated file to the env branch when the job succeeds. Default false: the file lands uncommitted in the worktree for review (manual runs see it; the deploy gate needs a commit).
Workforce component by numeric app id (the TIMBAL_APP_ID value;
number or string). At least one of component_id /
component_uid is required; when both are set they must resolve
to the same component.
Workforce component by manifest uid (the _id in timbal.yaml).
Optional steer for the generator, e.g. "focus on the refund flow".
Job kind. Defaults to "generate_initial" (the only kind today;
the vocabulary grows server-side without new endpoints).
Response
Job enqueued
Response body returned by the enqueue endpoint. The HTTP status is
202 Accepted — poll GET .../evals/jobs/{job_uid} for terminal
state (a succeeded generate_initial job's file then shows up on
GET .../evals/definitions with committed: false unless the job
committed).