Skip to main content
Purge cached files when you need visitors to see updated content immediately rather than waiting for cache expiration. You can purge the entire Pull Zone, or purge only files matching a specific tag.
Purging large zones puts temporary load on your origin server while content is re-cached. Performance may decrease briefly until edge nodes repopulate.

​
Dashboard

1

Open your Pull Zone

Go to your Pull Zone in the dashboard and click Purge Cache in the top right corner.
Purge cache button
2

Enter a search tag (optional)

Leave the search tag empty to purge the entire Pull Zone. If you enter a tag, only files with a matching CDN-Tag header are removed—the rest of your cache stays intact.
Purge cache by tag
3

Confirm the purge

Click Purge to clear the cache.

​
API

You can also purge cache programmatically. See the Core API reference for full details.

​
Full Pull Zone purge

curl -X POST "https://api.bunny.net/pullzone/{id}/purgeCache" \
  -H "AccessKey: YOUR_API_KEY"

​
Purge by tag

Tag responses from your origin with the CDN-Tag header, then purge all files matching that tag: 
curl -X POST "https://api.bunny.net/pullzone/{id}/purgeCache" \
  -H "AccessKey: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"CacheTag": "product-123"}'
Useful for invalidating all assets related to a specific product, user, or category without clearing your entire cache. To purge a specific URL across all pull zones, use the Purge URL endpoint in the Core API.

​
Rate limits

To ensure platform stability, the Purge API is protected by rate limits. These limits are designed to keep normal purge workflows fast while preventing abuse or accidental overload. Purge requests are rate-limited using a token bucket mechanism:
  • Limits are applied per account
  • Limits are applied per purge type
  • Each purge item consumes 1 token
  • Tokens refill steadily over time
If a request exceeds the available rate limit, the API returns a 429 Too Many Requests response with guidance on when to retry.

​
Purge types

Purge requests are classified into one of the following types: Exact Purge A single URL without wildcards where the path does not end with /. 
https://example.com/image.png
Prefix (Wildcard) Purge The URL contains a *, or the path ends with * or /. 
https://example.com/images/*
https://example.com/assets/

​
Default rate limits

Purge TypeBurst CapacityRefill RateApprox. Sustained Rate
Exact120 tokens5 tokens/sec~300 per minute
Prefix20 tokens0.5 tokens/sec~30 per minute
If your workload requires higher purge throughput, please contact support to discuss custom rate limits.

​
Perma-Cache behavior

If you’re using Perma-Cache:
  • Full zone purge: Clears CDN cache but Perma-Cache switches to a new directory (manually delete the old folder if needed)
  • Tag-based purging: Not supported with Perma-Cache enabled