Developers
Purge cache via API
The delivery purge API lets a deploy pipeline or CI job clear cached responses without a dashboard session. It authenticates with the tenant API key, reads its purge options from the API, and creates purge requests that the edge executes.
How it works
- Send the tenant API key as x-api-key or as a Bearer token
- GET /v1/delivery/purge/options returns the groups valid for the domain
- POST /v1/delivery/purge/requests with the group id and media paths
Good to know
- Customer JWT bearer tokens are not accepted on these endpoints — service tokens only
- Wildcards are rejected; use cache-rule purge groups for pattern-level purges
- A URL with a query string purges only that exact cached URL