seo-connect

GET /v1/seo-connection/cdn

The Zinn® CDN for this site — offered here or not, its zone, this month, its price.

All seo-connect endpoints

All developer docs →

Authentication

Send an API key as a bearer token. The endpoint checks sites.view; 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 GET 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

Zinn® SEO stage CDN1 (zs-658, owner decision Q182). A WordPress site hosted ELSEWHERE can serve its images, CSS, JavaScript and fonts from the Zinn® CDN (a Bunny pull zone pulling from the site's own https origin; the plugin rewrites static asset URLs to zone.hostname). offered is false for a site hosted with us (it keeps the Premium CDN tier) and for a site not on https://. price is derived from the vendor's cost at the 2x markup: USD micros per decimal GB per billing band, and the monthly minimum. Free. Needs seo.read.

Response

NameTypeRequiredWhat it is
hostedbooleanYesThe site is on Zinn® hosting (it keeps the Premium CDN tier).
httpsbooleanYes—
offeredbooleanYes—
zoneZinnCdnZone | nullYes—
priceZinnCdnPriceYes—
createdbooleanNoenableSeoCdn only: the zone was created by this call.

Errors this endpoint can return

401 · 403 · 429