reseller

POST `/v1/reseller/brand/sending-domain/verify`

Check your sending domain's DNS now.

Authentication

Send an API key as a bearer token. The key must carry the reseller.manage permission; a key without it is refused with 403, not 404.

Where your organisation id goes

This endpoint takes org_id as a query parameter. Leave it out and the call covers your whole tenancy subtree; send it to narrow the call to one organisation.

Your organisation id is on the API keys screen in your dashboard, beside the key itself. It is the same id in every call you make.

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/reseller/brand/sending-domain/verify \
  -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

Asks the mail provider to re-check your DNS and returns what it found. Requires `reseller.manage`. ⛔ The answer is the provider's, read back **after** the check rather than assumed from the trigger — "verifying" reads as progress and "still pending" reads as wait, and only one of them is true while your DNS is still propagating.

Parameters

Name	Type	Required	What it is
`org_id (query)`	`Uuid`	No	The organization this call acts on. Optional for a caller with exactly one direct membership; required for anyone with more than one — which is every reseller and every agen…

Response

Name	Type	Required	What it is
`domain`	`string`	Yes	—
`verified`	`boolean`	Yes	The mail provider's answer. Never inferred from `domain` being set.
`provider`	`string`	Yes	—
`provider_status`	`string`	Yes	The provider's raw status word, for display. Never branch on it.
`records`	`BrandDnsRecord[]`	Yes	—

Errors this endpoint can return

401 · 403 · 404 · 429 · 503