Get DNS records
const url = 'https://qinto-api.blotout.io/teams/7b8d1a52-6c1e-4b6f-9a30-2f8a54d1c3e9/domains/3f2a9c81-5d47-4e0b-8c66-91b2a7f04d15/dns';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://qinto-api.blotout.io/teams/7b8d1a52-6c1e-4b6f-9a30-2f8a54d1c3e9/domains/3f2a9c81-5d47-4e0b-8c66-91b2a7f04d15/dns \ --header 'Authorization: Bearer <token>'Returns the DNS records a customer must publish for a site, and whether they have taken effect. This is what to poll while waiting for a domain to verify.
How it works
This operation only reads, so it is safe to call as often as you like. Use POST /dns/check to force a refresh after publishing records. A site Qinto attaches itself needs no records and reports required: false. When the lookup cannot run the response is still 200 with checked: false; read failureKind — host_not_ready and not_configured need a fix before retrying, anything else is worth retrying as-is.
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.
Responses
Section titled “Responses”The site’s DNS records and verification state, including a state that could not be determined.
A site’s DNS records and its current verification state.
object
Records the customer must publish; empty when the site needs none or the check could not run.
One DNS record the customer must publish.
object
Record type to create.
Record name, relative to the customer’s root domain.
Value the record must carry.
Extra instruction for this record, when one applies.
Whether the site’s hostname is verified and serving.
Whether this site needs DNS at all. False when Qinto attaches the hostname itself, which never verifies through DNS.
Whether the check ran. False means the state is unknown — read message and failureKind rather than trusting valid.
Why the check could not run, or null when it did: host_not_ready and not_configured need a fix before retrying, anything else is transient.
What is outstanding, or why the check could not run. Empty once the site is verified.
Example
{ "records": [ { "type": "CNAME", "name": "shop", "value": "shop.customers.qinto-edge.com", "note": "Disable the Proxied (orange-cloud) option." } ], "valid": false, "required": true, "checked": true, "failureKind": "host_not_ready", "message": "Pending SSL validation."}invalid_params — A path parameter failed validation (for example a malformed UUID); details pinpoints the offending parameter.
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"}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"}