Current endpoints
GET /api/v1/certificatesPOST /api/v1/certificatesGET /api/v1/certificates/{certificateId}POST /api/v1/verifyGET /api/v1/works/{isrc}GET /api/v1/search?q={query}GET /api/v1/anchorsGET /api/v1/ledger/eventsACC API
ACC API is the product surface for distributors, DSPs, labels, catalog owners and licensing teams that need certificate category, status, hashes, declaration version and verification URL inside their own workflows.
GET /api/v1/certificatesPOST /api/v1/certificatesGET /api/v1/certificates/{certificateId}POST /api/v1/verifyGET /api/v1/works/{isrc}GET /api/v1/search?q={query}GET /api/v1/anchorsGET /api/v1/ledger/eventsPilot authentication is designed around bearer partner keys. Public review endpoints remain open for validation; partner access requests can already identify the calling partner and appear in audit logs.
Request API pilotPublic review endpoints work without auth for partner validation.
Partner access requests can send Authorization: Bearer acc_partner_review.
Production pilots receive partner-specific bearer keys, audit partnerId and agreed rate limits.
ACC_REQUIRE_PARTNER_AUTH=true can gate the API without changing client paths.
Authorization: Bearer acc_partner_reviewPublic review endpoints are protected by lightweight rate limits. Partner pilots will receive explicit limits, partner IDs and audit exports before any production integration.
Recommended pilot start: one workflow, one catalog subset, one integration owner and one expected decision that ACC status should improve.
{
"valid": true,
"status": "anchored",
"matchedCertificateId": "ACC-2026-023F0159",
"certificate": {
"category": "HUMAN",
"identityAssuranceLevel": "LEVEL_2_SIGNED_DECLARATION",
"work": {
"declaredProducerName": "Mira Nowak",
"isrc": "PL2O52600001",
"isrcDisplay": "PL-2O5-26-00001",
"isrcSource": "acc_assigned",
"isrcAssignedBy": {
"name": "Art Clearance Certification Sp. z o.o."
}
},
"anchorBatch": { "status": "anchored" }
},
"auth": {
"partnerId": "public-partner-review",
"mode": "partner_key",
"authenticated": true
}
}{
"isrc": "USRC17607839",
"accStatus": "not_certified",
"certificates": [],
"externalLookup": {
"source": "MusicBrainz",
"found": true
}
}HTTP 401. Invalid partner API key when auth is required.
HTTP 400. Required certificate, hash or declaration field is missing or malformed.
HTTP 404. Certificate or anchor batch does not exist.
HTTP 429. Request volume exceeded the controlled-access safety limit.
HTTP 503. ACC Core could not answer and no local fallback was available.
Integration path
A pilot can start with a small ISRC list, upload workflow, catalog subset or licensing scenario. The output is a certificate status object, public proof URL and ledger/anchor state that your system can read.
ACC API response field.
ACC API response field.
ACC API response field.
ACC API response field.
ACC API response field.
ACC API response field.
ACC API response field.
ACC API response field.
ACC API response field.
ACC API response field.
ACC API response field.
ACC API response field.
ACC API response field.