Authentication
Send an API key as a bearer token. The key must carry the sites.cache.purge permission; 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/domains/{domainId}/cache/purge \
-H "Authorization: Bearer zdk_live_…" \
-H "Content-Type: application/json" \
-d '{ }'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
Purge the CDN cache for a domain now. Omit `urls` to purge everything, or pass a bounded list of absolute URLs to purge only those. Exposed on the dashboard and the MCP server through the same service, so the two cannot diverge (docs/19 §5.4). A domain not served through our CDN is a `404`. Requires `sites.cache.purge`.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
domainId (path) | Uuid | Yes | The domain's id. |
Request body
| Name | Type | Required | What it is |
|---|---|---|---|
urls | string[] | No | Absolute URLs to purge. Omit or empty to purge all cached content. |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
purged | boolean | Yes | — |
urls | integer | Yes | How many URLs were targeted (0 = a full purge). |
Errors this endpoint can return
401 · 403 · 404 · 429