Share DNS instructions
const url = 'https://qinto-api.blotout.io/teams/7b8d1a52-6c1e-4b6f-9a30-2f8a54d1c3e9/domains/3f2a9c81-5d47-4e0b-8c66-91b2a7f04d15/dns/share';const options = { method: 'POST', headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'}, body: '{"emails":["dns-admin@example.com","ops@example.com"],"submissionId":"7c9e6679-7425-40de-944b-e07fc1f90ae7"}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://qinto-api.blotout.io/teams/7b8d1a52-6c1e-4b6f-9a30-2f8a54d1c3e9/domains/3f2a9c81-5d47-4e0b-8c66-91b2a7f04d15/dns/share \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "emails": [ "dns-admin@example.com", "ops@example.com" ], "submissionId": "7c9e6679-7425-40de-944b-e07fc1f90ae7" }'Emails a site’s outstanding DNS records to the people who administer its domain. Use it when whoever is setting the site up cannot edit DNS themselves.
How it works
Recipients always get the current records, and the email names the API token that shared them. Recipients are lowercased and de-duplicated before sending, and sent reports how many distinct addresses were mailed. A site served on a Qinto URL needs no DNS changes and returns no_dns_records. Sends are rate limited per API token and per site; exceeding either returns rate_limited and delivers nothing.
Required permissions
domain:readon all domains, or on the addressed domain when its id is in the route
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Unique id (UUID) of the team that owns the addressed resources, as shown in the team settings on the Blotout platform.
Example
7b8d1a52-6c1e-4b6f-9a30-2f8a54d1c3e9Unique id (UUID) of the team that owns the addressed resources, as shown in the team settings on the Blotout platform.
Unique id (UUID) of the site, as returned by the create and list operations.
Example
3f2a9c81-5d47-4e0b-8c66-91b2a7f04d15Unique id (UUID) of the site, as returned by the create and list operations.
Request Bodyrequired
Section titled “Request Bodyrequired”Who to send the instructions to, and the id identifying this send for safe retries.
object
Addresses to send the instructions to, between 1 and 10. Duplicates and case variants are collapsed before sending.
Example
[ "dns-admin@example.com", "ops@example.com"]Caller-generated UUID identifying this send. Reuse the same value to retry safely within 24 hours, provided the recipients, the site’s current DNS records and the sharing user are unchanged; anything else is treated as a new send and delivers a second email. Generate a new value to deliberately send again.
Example
7c9e6679-7425-40de-944b-e07fc1f90ae7Responses
Section titled “Responses”The instructions were sent; the response reports how many distinct addresses were mailed.
object
Number of distinct addresses the instructions were sent to, after duplicates were collapsed.
Example
{ "sent": 2}invalid_params — A path parameter failed validation (for example a malformed UUID); details pinpoints the offending parameter. invalid_body — The JSON body is unparseable or failed schema validation; details pinpoints the offending fields when the body could be parsed.
object
Machine-readable error slug; switch on this value rather than on the HTTP status alone.
Field-level validation errors: a tree keyed by input property, each node carrying an errors array of human-readable messages. Render it to help the caller correct the request.
object
Example
{ "error": "invalid_params", "details": { "errors": [], "properties": { "teamId": { "errors": [ "Invalid UUID" ] } } }}unauthenticated — The Authorization: Bearer token is missing, malformed, or no longer valid. Generate a team API token or obtain a new OAuth access token.
object
Machine-readable error slug; switch on this value rather than on the HTTP status alone.
Example
{ "error": "unauthenticated"}forbidden — The bearer credential lacks the required permission or belongs to another team, or its user lacks the organization role a developer operation needs. Update its policies, use a credential bound to the addressed team, or ask an organization owner for the role; message states the reason when one is known.
object
Machine-readable error slug; switch on this value rather than on the HTTP status alone.
Human-readable reason for this specific failure, intended for display — do not parse it programmatically.
Example
{ "error": "forbidden", "message": "The Cloudflare API token is invalid or expired."}not_found — The addressed resource does not exist within this team; check the id and retry.
object
Machine-readable error slug; switch on this value rather than on the HTTP status alone.
Example
{ "error": "not_found"}no_dns_records — The site needs no DNS changes, so there are no instructions to share; it is served on a Qinto URL or its records are already in place.
object
Machine-readable error slug; switch on this value rather than on the HTTP status alone.
Example
{ "error": "no_dns_records"}host_not_ready — The site’s host is not ready to serve it — no Cloudflare zone chosen, no stored API token, a token scoped to the wrong zone, a conflicting DNS record, or a dispatcher that refused the request. message names the fix.
object
Machine-readable error slug; switch on this value rather than on the HTTP status alone.
Human-readable reason for this specific failure, intended for display — do not parse it programmatically.
Example
{ "error": "host_not_ready", "message": "The Cloudflare API token is invalid or expired."}rate_limited — Too many requests for this API token or site in a short window; wait a minute and retry.
object
Machine-readable error slug; switch on this value rather than on the HTTP status alone.
Example
{ "error": "rate_limited"}internal — Unexpected server error. Nothing is guaranteed to have been persisted; idempotent operations are safe to retry.
object
Machine-readable error slug; switch on this value rather than on the HTTP status alone.
Example
{ "error": "internal"}upstream_unavailable — A provider Qinto depends on (Cloudflare for the DNS records, or the email service) could not be reached or refused the request. Delivery is unconfirmed rather than ruled out — a lost response can follow an accepted send — so retry with the same submissionId, which de-duplicates an identical retry at the provider.
object
Machine-readable error slug; switch on this value rather than on the HTTP status alone.
Example
{ "error": "upstream_unavailable"}