Create purge

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

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_everythingbodyboolean—Everything drops the zone's entire edge cache.
zonebodystring—Zone is the 32-hex Cloudflare zone id, from the path.

Response

StatusBodyMeaning
200ok
defaultproblem-detailsrefused

200 body — 1 field.

FieldInTypeAlwaysDescription
(body)bodyanyyes

Failure carries the platform error shape — see Errors.

Examples

hanzo cloudflare zones purge <zone>
import { Configuration, CloudflareApi } from 'hanzoai';

const api = new CloudflareApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postCloudflareZonesByZonePurge({ zone: 'zone', files: ["<files>"], purge_everything: false });
from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import CloudflareApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = CloudflareApi(client).post_cloudflare_zones_by_zone_purge(zone='zone', files=["<files>"], purge_everything=False)
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.CloudflareAPI.PostCloudflareZonesByZonePurge(context.Background()).Execute()
if err != nil {
	return err
}
use hanzo_client::apis::{configuration::Configuration, cloudflare_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = cloudflare_api::post_cloudflare_zones_by_zone_purge(&cfg, Default::default()).await?;
import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.CloudflareApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new CloudflareApi(client).postCloudflareZonesByZonePurge();
curl -X POST https://api.hanzo.ai/v1/cloudflare/zones/<zone>/purge \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "files": [
         "<files>"
       ],
       "purge_everything": false
     }'

MCP reaches cloudflare through the cloudflare tool, which names its 29 operations with its own verbs — this one among them, under a name only MCP declares. describe explains any of them:

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "describe",
         "arguments": {
           "op": "list_cloudflare_d1_databases"
         }
       }
     }'

Cloudflare API · All Hanzo APIs · Interactive reference

Was this page useful?