visibility

POST /v1/domain-vetting/reports/bulk

Vet up to 25 domains as one run — spends one credit per new report.

All visibility endpoints

All developer docs →

Authentication

Send an API key as a bearer token. The endpoint checks sites.create; 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 POST https://api.zinndigital.com/v1/domain-vetting/reports/bulk \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "domains": <string[]> }'

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

V1 run_many parity. Every domain is validated and the credits for the NEW reports are counted before any is taken, so a run the organisation cannot pay for in full is refused with 403 and takes nothing. A domain vetted in the last reuse_days returns its report free (reused). ONE e-mail goes out when the last report of the run has finished. 422 for more than 25 domains, one that is not a domain, or an unknown market.

Request body

NameTypeRequiredWhat it is
domainsstring[]Yes—
location_codeintegerNo—

Response

NameTypeRequiredWhat it is
reportsDomainVetSummary[]Yes—
createdintegerYesNew reports started (each took one credit).
reusedintegerYesRecent reports returned free.

Errors this endpoint can return

400 · 401 · 403 · 404 · 422 · 503