GET /v1/registry-documents/{token}

Authentication

This endpoint is public. It takes no credential and no organisation — it is what our own marketing site and AI answer engines read.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X GET https://api.zinndigital.com/v1/registry-documents/{token}

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

The link our verification team hands the registrar after approving a case. The token is 256 random bits, stored only as a hash, valid for 7 days, and dead as soon as the case closes or staff re-issue links. Every fetch is audit-logged. Any invalid, expired or revoked token answers the same 404. Served as a download (Content-Disposition: attachment, nosniff, a sandboxing CSP).

Parameters

Errors this endpoint can return

404