seo-connect

POST /v1/seo-connection/cdn/purge

Drop everything the site's Zinn® CDN has cached. Free.

All seo-connect endpoints

All developer docs →

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/purge \
  -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

The next request for each file is read from the site again. Called by the plugin's purge button and when the site's media, theme or plugins change. 404 when the CDN is not on. Audited. Needs seo.run.

Response

NameTypeRequiredWhat it is
purgedbooleanYes—
hostnamestringYes—

Errors this endpoint can return

401 · 403 · 404 · 429 · 503