Create several eval cases
Adds up to 100 cases to the suite in one call — the bulk form of the single create, and the way to import a suite or convert a repo's test files without a round trip per case. Every entry needs a title and a non-empty steps array. Cases are validated together and reported individually: a failed entry does not roll back its committed siblings, so the response is 201 even when some entries were refused — read failed rather than branching on the status alone. Send an Idempotency-Key header to make a retry land on the same rows.
Path parameters
ID of the hosted project that contains the server.
Eval suite ID, as returned by POST /eval-runs.
Headers
Makes the write retry-safe. A repeat of the same request under the same key lands on the rows the first attempt authored instead of creating a second copy; those entries come back with replayed: true.
Request body
Response
Per-case outcomes. Some entries may have failed; see failed.
Changes
Changed in 4 of the 80 revisions of this API.15
- ○
added the new optional request property
cases/items/intentnew-optional-request-property
- ○
- ●
added the new
INVALID_IMPORTenum value to thefailed/items/coderesponse property for the response status201response-property-enum-value-added
- ○
added the new optional request property
cases/items/importnew-optional-request-property
- ●
- ○
added the new optional request property
cases/items/passThresholdnew-optional-request-property
- ○
added the new optional request property
cases/items/repetitionsnew-optional-request-property
- ○
- ○
endpoint added
endpoint-added
- ○