Hanzo
OpenapiCloudflare

Drops a zone's Cloudflare edge cache — either the whole zone (purge_everything)…

Drops a zone's Cloudflare edge cache — either the whole zone (purge_everything) or exactly the listed file URLs. Requires org admin.

POST /v1/cloudflare/zones/{zone}/purge

Addresshttps://api.hanzo.ai/v1/cloudflare/zones/{zone}/purge
MethodPOST
Operationpost_cloudflare_zones_by_zone_purge
AuthAuthorization: Bearer $HANZO_API_KEY

Drops a zone's Cloudflare edge cache — either the whole zone (purge_everything) or exactly the listed file URLs. Requires org admin.

Purging is the one zone-scoped WRITE this plane owns. It is not DNS — no record changes — so it does not belong on /v1/dns, and it is not a connection, so it does not belong on the integrations plane. It is a cache operation on a zone, which is what this asset plane is for. It takes the admin gate because dropping a zone's cache sends every subsequent request to the origin: on a site fronting a small origin that is a self-inflicted load spike, so it is a change, not a look.

Exactly one selector is required. Cloudflare treats a body with neither as a no-op and answers 200, which reads as "purged" to a caller that never purged anything — the failure we refuse to pass through.

Request

4 fields, body application/json (required).

FieldInTypeRequiredDescription
zonepathstringyesZone is the 32-hex Cloudflare zone id, from the path.
filesbodystring[]Files purges exactly the listed URLs — at most 30, Cloudflare's per-request cap.
purge_everythingbodybooleanEverything drops the zone's entire edge cache.
zonebodystringZone is the 32-hex Cloudflare zone id, from the path.

Response

StatusBodyMeaning
200ok

200 body — 1 field.

FieldInTypeAlwaysDescription
(body)bodyanyyes

Failure carries the platform error shape — see Errors.

Examples

hanzo cloudflare zones purge <zone>

Cloudflare API · All Hanzo APIs · Interactive reference

How is this guide?

On this page