Associate an existing check with a target without running or approving it

POST/v1/quality/targets/{targetType}/{targetId}/checks

Requires target edit access, check evidence read access and agents write permission. Current permissions are rechecked on retries. The organization/target/check tuple is the idempotency identity. Execution-dispatch credentials cannot change Quality setup. The relation is a declared association, not verified execution lineage.

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
targetTypepathmetronome | function | agentYes
targetIdpathstringYes
Query parameters
None.

Body schema

Content type: application/json · Required

FieldTypeRequiredDescription
checkKindassertion | benchmarkYes
checkIdstringYes

What the API returns

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

200Retained association or identical retry; no check or target executionapplication/json
FieldTypeRequiredDescription
associationobjectYes
association.idstringYesUnique identifier.
association.targetTypemetronome | function | agentYes
association.targetIdstringYes
association.checkKindassertion | benchmarkYes
association.checkIdstringYes
association.provenancedeclared_associationYes
association.createdAtstringYesISO 8601 timestamp.
400Invalid definition or unknown fields
None.
401Authentication required
None.
403Organization
None.
404Target edit or check evidence permission unavailable
None.
409Association could not be retained
None.
503Durable Quality setup unavailable; retry the same association
None.
Associate an existing check with a target without running or approving it
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow