Sync the WFP account
const url = 'https://qinto-api.blotout.io/teams/7b8d1a52-6c1e-4b6f-9a30-2f8a54d1c3e9/hosts/3f2a9c81-5d47-4e0b-8c66-91b2a7f04d15/wfp-sync';const options = {method: 'POST', 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 POST \ --url https://qinto-api.blotout.io/teams/7b8d1a52-6c1e-4b6f-9a30-2f8a54d1c3e9/hosts/3f2a9c81-5d47-4e0b-8c66-91b2a7f04d15/wfp-sync \ --header 'Authorization: Bearer <token>'Finishes preparing the host’s Cloudflare account for Workers-for-Platforms hosting. Call it to retry a create or a zone change that reported a not-pushed wfpSync outcome.
How it works
Every step is idempotent, so the call is safe to repeat until it succeeds. A host without WFP enabled answers not_found.
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.
Responses
Section titled “Responses”The sync was attempted; the outcome reports whether it landed.
object
Outcome of pushing the account’s Workers-for-Platforms control-token registry to its dispatcher.
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
{ "wfpSync": { "pushed": true, "reason": "configuration_failed" }}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"}