Set the host zone
const url = 'https://qinto-api.blotout.io/teams/7b8d1a52-6c1e-4b6f-9a30-2f8a54d1c3e9/hosts/3f2a9c81-5d47-4e0b-8c66-91b2a7f04d15/zone';const options = { method: 'POST', headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'}, body: '{"zoneDomain":"agency.example.com"}'};
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/hosts/3f2a9c81-5d47-4e0b-8c66-91b2a7f04d15/zone \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "zoneDomain": "agency.example.com" }'Records which Cloudflare zone a host serves customer traffic from. Call it when a create or update returned a zoneRequired list, choosing one of its names.
How it works
The zone must exist in the host’s Cloudflare account, otherwise the request fails with invalid_credentials and nothing is written. Once recorded, customers point their CNAME records at <subdomain>.customers.<zoneDomain>. The zone cannot be changed once a site references the host: that attempt fails with in_use. A wfp_route_cleanup_failed leaves the zone as it was and is safe to retry; a wfpSync that reports not pushed can be retried with the sync operation.
Required permissions
team:writeon the team
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 host, as returned by the create and list operations.
Example
3f2a9c81-5d47-4e0b-8c66-91b2a7f04d15Unique id (UUID) of the host, as returned by the create and list operations.
Request Bodyrequired
Section titled “Request Bodyrequired”The zone the host serves its customers from.
The Cloudflare zone this host serves its customers from.
object
Zone to serve customer traffic from. It must exist in the host’s Cloudflare account — send one of the names the zoneRequired list returned. It cannot be changed once a site references this host.
Example
agency.example.comResponses
Section titled “Responses”The zone was recorded; the response echoes the host and any WFP provisioning outcome.
object
A Cloudflare account connected to the team. The API token that authorizes it is write-only and never part of this shape.
object
Server-assigned unique id of the host. Address the host with it in the get, update and delete operations.
Display name of the host, as shown on the Blotout platform.
Id of the Cloudflare account this host manages. It is fixed when the host is created.
Cloudflare zone this host serves customer traffic from. Custom hostnames are created on it, and customers point their CNAME records at <subdomain>.customers.<zoneDomain>. Null until a zone is chosen — set it with the zone operation.
Whether the account participates in Workers for Platforms — it hosts multiple customer workers behind the Qinto dispatcher (for example, an agency account).
When the host was connected to the team, as an ISO 8601 UTC timestamp.
Outcome of pushing the account’s Workers-for-Platforms control-token registry to its dispatcher. Null when the host does not participate in Workers for Platforms.
object
Whether the account’s control-token registry reached its dispatcher.
Why provisioning stopped: zone_required means no zone is chosen yet, so nothing was provisioned; custom_hostnames_disabled means the zone’s plan does not include Cloudflare for SaaS; fallback_origin_failed, subdomain_failed, namespace_failed, dispatcher_failed, and route_failed name the account-provisioning step that errored; qinto_url_failed names a step that only runs for Qinto-managed hosting, so it never appears here; dispatcher_missing and push_failed mean the token-registry push itself did not land; bundles_missing means the Blotout platform deployment is missing its released worker bundles; registry_busy means another rewrite of the account’s control-token registry — a token rotation, its cleanup, or another deploy — was running, so the dispatcher deploy stepped aside. Every step is idempotent, so syncing again retries the whole provisioning. configuration_failed requires checking account credentials and hosting settings; shared_dispatcher_missing means EdgeTag removed shared hosting, which Qinto will not recreate. Contact the account operator. Absent when pushed is true.
Example
{ "host": { "hostId": "3f2a9c81-5d47-4e0b-8c66-91b2a7f04d15", "name": "Production", "accountId": "023e105f4ecef8ad9ca31a8372d0c353", "zoneDomain": "agency.example.com", "wfp": false, "createdAt": "2026-06-18T00:00:00.000Z" }, "wfpSync": { "pushed": true, "reason": "configuration_failed" }}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"}in_use — The resource is still referenced by other resources and cannot be deleted; remove the dependents first. wfp_route_cleanup_failed — The dispatcher route on the host’s Cloudflare zone could not be removed, so the operation was refused rather than leave the zone routing all of its traffic to Qinto; retry once Cloudflare is reachable.
object
Machine-readable error slug; switch on this value rather than on the HTTP status alone.
Example
{ "error": "in_use"}invalid_credentials — The host details failed verification: Cloudflare rejected the account id and API token, the name duplicates an existing host in the team, or (on update) no token is stored to verify with. message states the exact reason.
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": "invalid_credentials", "message": "The Cloudflare API token is invalid or expired."}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"}