# Purge a Cloudflare zone's cache

> POST /api/cloudflare/zones/{zoneId}/cache on the Vigilbase One API.

Source: https://docs.vigilbase.com/one/api/reference/cloudflare/post-cloudflare-zones-zone-id-cache

`POST https://one.vigilbase.com/api/cloudflare/zones/{zoneId}/cache`

> Needs a recent sign-in: renewing a token doesn't count, and MCP sessions and API keys are always refused. See [changes that need a recent sign-in](https://docs.vigilbase.com/one/api#changes-that-need-a-recent-sign-in).

## Authorizations

- `Authorization` (string, header, required): Bearer access token from Vigilbase Identity (`auth.vigilbase.com`), sent as `Authorization: Bearer <token>`. The CLI gets one with `vigilbase login`. Organisation API keys can't call this endpoint: it needs a recent sign-in by a person.
- Permissions checked: `write:deployments`, `write:services`

## Path parameters

- `zoneId` (string, required)

## Body (application/json)

- `customerId` (string, required): Min length 1.
- `accountId` (string, required): Min length 1.
- `purgeEverything` (boolean)
- `files` (string[])
- `tags` (string[])
- `hosts` (string[])
- `prefixes` (string[])

## Responses

### 200

Success

### 401

Authentication required

### 403

Not permitted

## Example request

```bash
# Token from `vigilbase login`. API keys can't call this.
curl --request POST \
  --url 'https://one.vigilbase.com/api/cloudflare/zones/{zoneId}/cache' \
  --header "Authorization: Bearer $VIGILBASE_TOKEN" \
  --header 'Content-Type: application/json' \
  --data '{"customerId":"<string>","accountId":"<string>","purgeEverything":true,"files":["<uri>"],"tags":["<string>"],"hosts":["<string>"],"prefixes":["<string>"]}'
```