visibility

GET /v1/domain-vetting/reports/{report_id}

One domain vetting report — verdict, reasons and evidence.

All visibility endpoints

All developer docs →

Zinn®, our Viking, hammering at his anvil beside an API endpoint sending events to several listeners.

Authentication

Send an API key as a bearer token. The endpoint checks sites.view; a key without it is refused with 403, not 404.

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/domain-vetting/reports/{report_id} \
  -H "Authorization: Bearer zdk_live_…"

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 report as it stands. While status is queued or running poll again. A complete or partial report carries a 0-100 score, a verdict (clean, care, risk), the reasons behind it (worst first, each a stable code with params the screen renders in the reader's language) and the evidence in parts. missing names the parts that could not be read this time; they are left out of the score, never scored as clean. A null score means "not scored", never zero.

Parameters

NameTypeRequiredWhat it is
report_id (path)stringYes—

Response

NameTypeRequiredWhat it is
reportDomainVetReportYes—

Errors this endpoint can return

401 · 403 · 404 · 422