Purge 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.

Overview

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
• The path does not end with /

Example:

https://example.com/image.png

Prefix (Wildcard) Purge

• The URL contains a *, or
• The path ends with * or /

Examples:

https://example.com/images/*
https://example.com/assets/

Default Rate Limits

Need Higher Limits?

If your workload requires higher purge throughput, please contact support to discuss custom rate limits.