Download a self-contained HTML review of the exact target-context report

GET/v1/quality/targets/{targetType}/{targetId}/report/export

Rechecks target and child evidence access. Requires the report fingerprint previously reviewed. The same bounded report model drives screen and export; associations never attest imported target provenance. No workflow or grading execution, source archive or release approval.

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
NameLocationTypeRequiredDescription
fingerprintquerystringYes

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.

200Downloadable HTML with unchanged evidence identityapplication/json
FieldTypeRequiredDescription
exportobjectYes
export.schemaVersioncomputer_agents_quality_report_export_v1Yes
export.filenamestringYes
export.contentTypetext/html; charset=utf-8Yes
export.reportFingerprintstringYes
export.contentFingerprintstringYes
export.contentstringYesInert self-contained HTML; exact UTF-8 bytes are identified by contentFingerprint
400Invalid or missing expected fingerprint
None.
401Authentication required
None.
403Organization or coarse permission unavailable
None.
404Target read permission unavailable
None.
409Report changed or retained evidence integrity failed
None.
503Durable report capability unavailable
None.
Download a self-contained HTML review of the exact target-context report
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow