| [ Web Proxy ] |
| Viewing: https://developers.cloudflare.com/api/resources/cache/methods/purge | [Back] [Original] |
Removes ALL files from Cloudflares cache. All tiers can purge everything.
{"purge_everything": true}
Granularly removes one or more files from Cloudflares cache by specifying URLs. All tiers can purge by URL.
To purge files with custom cache keys, include the headers used to compute the cache key as in the example. If you have a device type or geo in your cache key, you will need to include the CF-Device-Type or CF-IPCountry headers. If you have lang in your cache key, you will need to include the Accept-Language header.
NB: When including the Origin header, be sure to include the scheme and hostname. The port number can be omitted if it is the default port (80 for http, 443 for https), but must be included otherwise.
Single file purge example with files:
{"files": ["http://www.example.com/css/styles.css", "http://www.example.com/js/index.js"]}
Single file purge example with url and header pairs:
{"files": [{"url": "http://www.example.com/cat_picture.jpg", "headers": {"CF-IPCountry": "US", "CF-Device-Type": "desktop", "Accept-Language": "zh-CN"}}, {"url": "http://www.example.com/dog_picture.jpg", "headers": {"CF-IPCountry": "EU", "CF-Device-Type": "mobile", "Accept-Language": "en-US"}}]}
Granularly removes one or more files from Cloudflares cache either by specifying the host, the associated Cache-Tag, or a Prefix.
Flex purge with tags:
{"tags": ["a-cache-tag", "another-cache-tag"]}
Flex purge with hosts:
{"hosts": ["www.example.com", "images.example.com"]}
Flex purge with prefixes:
{"prefixes": ["www.example.com/foo", "images.example.com/bar/baz"]}
Please refer to purge cache availability and limits documentation page.
The preferred authorization scheme for interacting with the Cloudflare API. Create a token.
Authorization: Bearer Sn3lZJTBX6kkg7OdcBUAxOO963GEIyGQqnFTOFYYThe previous authorization scheme for interacting with the Cloudflare API, used in conjunction with a Global API key.
X-Auth-Email: user@example.comThe previous authorization scheme for interacting with the Cloudflare API. When possible, use API tokens instead of Global API keys.
X-Auth-Key: 144c9defac04969c7bfad8efaa8ea194Cache PurgeFor more information on cache tags and purging by tags, please refer to purge by cache-tags documentation page.
For more information purging by hostnames, please refer to purge by hostname documentation page.
For more information on purging by prefixes, please refer to purge by prefix documentation page.
For more information, please refer to purge everything documentation page.
For more information on purging files, please refer to purge by single-file documentation page.
For more information on purging files with URL and headers, please refer to purge by single-file documentation page.
curl https://api.cloudflare.com/client/v4/zones/$ZONE_ID/purge_cache \
-H 'Content-Type: application/json' \
-H "Authorization: Bearer $CLOUDFLARE_API_TOKEN" \
-d '{
"tags": [
"a-cache-tag",
"another-cache-tag"
]
}'{
"errors": [
{
"code": 1000,
"message": "message",
"documentation_url": "documentation_url",
"source": {
"pointer": "pointer"
}
}
],
"messages": [
{
"code": 1000,
"message": "message",
"documentation_url": "documentation_url",
"source": {
"pointer": "pointer"
}
}
],
"success": true,
"result": {
"id": "023e105f4ecef8ad9ca31a8372d0c353"
}
}{
"errors": [
{
"code": 1000,
"message": "message",
"documentation_url": "documentation_url",
"source": {
"pointer": "pointer"
}
}
],
"messages": [
{
"code": 1000,
"message": "message",
"documentation_url": "documentation_url",
"source": {
"pointer": "pointer"
}
}
],
"success": true,
"result": {
"id": "023e105f4ecef8ad9ca31a8372d0c353"
}
}| Web Proxy Viewer | New URL | Original Page |