Append iterations to an open run
Appends one batch of iteration results to a run opened by runs/start.
How eval runs executed OUTSIDE the platform (local dev, CI) reach the Evals dashboard. Authenticate like any other /api/v1 route (typically an sk_ key); the gateway swaps in a delegated org-scoped token so the backend's fail-closed org scoping applies.
The {projectId} segment declares where results land and always wins over any projectId in the body. The literal default resolves to the key org's Default project — the zero-config CI case.
STATUS AND BODY PASS THROUGH VERBATIM: success shapes are the legacy { ok: true, ... } envelopes the SDK reporter parses, not the v1 resource envelope.
Path parameters
Project id, or the literal default for the key org's Default project.
Request body
Forwarded VERBATIM to the backend's eval-ingestion surface, which owns the schema. The projectId path segment always wins: it overwrites any projectId in the body, and the literal default omits it so the key's org Default project is used. Bodies are capped at ~6 MiB here and 5 MiB by the backend.
Response
The backend's response, passed through.
The backend's response, passed through verbatim along with its status code. Success shapes are the legacy { ok: true, ... } envelopes the SDK reporter parses — deliberately NOT the v1 resource envelope. Errors are canonical v1 { code, message }.