List accepted Evaluation case checkpoints

GET/v1/evaluations/runs/{runId}/checkpoints

Read durable case results with independent run-result authorization. Checkpoints are progress records; only a terminal Evaluation report produces release evidence.

How to call this endpoint

Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.

Path, query, and header parameters

These parameters control which ACP object the endpoint acts on and how the request is processed.

Path parameters
NameLocationTypeRequiredDescription
runIdpathstringYes
Query parameters
NameLocationTypeRequiredDescription
caseIdquerystringNoRetrieve one accepted case by its immutable identifier.
limitqueryintegerNo
offsetqueryintegerNo

Body schema

This endpoint does not require a request body.

None.

What the API returns

Each response code below includes the documented payload shape for the ACP API.

200Accepted case results ordered by case ID, at most 2000000 bytes eachapplication/json
FieldTypeRequiredDescription
objectlistYes
dataobject[]Yes
data[].caseIdstringYes
data[].resultobjectYes
data[].result.caseIdstringYes
data[].result.namestringNoHuman-readable name.
data[].result.statuspassed | failed | error | skippedYesCurrent lifecycle status.
data[].result.scorenumberNo
data[].result.outputobjectNo
data[].result.explanationstringNo
data[].result.errorstringNo
data[].result.durationMsintegerNo
data[].result.evaluatorobjectNo
data[].result.metadataobjectNoFree-form metadata object.
data[].resultFingerprintstringYes
data[].bindingFingerprintstringYes
data[].evaluatorFingerprintstringYes
data[].systemFingerprintstringYes
data[].acceptedAtstringYes
hasMorebooleanYes
nextOffsetintegerYes
401Authentication required
None.
404Run not found or inaccessible
None.
List accepted Evaluation case checkpoints
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow