POST /v1/seo-connection/cdn

Authentication

Send an API key as a bearer token. The endpoint checks sites.create; a key without it is refused with 403, not 404.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

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/seo-connection/cdn \
  -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

Creates (or finds) the site's pull zone and answers with its hostname (201 when created, 200 when it already existed or was switched back on). ⛔ Nothing is charged at the click: each UTC day's traffic is charged afterwards from Zinn® credit at the 2x markup, and each month is topped up to a pro-rated minimum. Refused with nothing created: a site hosted with us (409, it keeps the Premium CDN), a site not on https (422), credit below one month's minimum (422, refusal.zinnCdn.noCredit), an account not in good standing (403). Audited. Needs seo.spend.

Response

Errors this endpoint can return

401 · 403 · 409 · 422 · 429 · 503