Check rate and object limit statuses
POST https://{{host}}/ccu/v3/rate-limit-status/:purge-type
The Fast Purge API uses a token bucket model for rate limiting to protect itself from inadvertent or malicious overuse. For each Akamai account, there's a rate limit shared by all object types (CP codes, cache tags, and URL/ARLs), and three separate resource limits for each object type. Each purge request uses one rate limit token from the requests bucket. Each purge object in a request takes up a token from the resource bucket. This operation fetches information on the remaining number of requests and objects for a specific account. You can use these details to monitor the request consumption or throttle requests to prevent exceeding the limits, which results in the 429 error.
Request Params
Key | Datatype | Required | Description |
---|---|---|---|
accountSwitchKey | string | (Optional) For customers who manage more than one account, this runs the operation from another account. The Identity and Access Management API provides a list of available account switch keys. |
HEADERS
Key | Datatype | Required | Description |
---|---|---|---|
Accept | string |
RESPONSES
status: Created
{"detail":"Request accepted","estimatedSeconds":5,"httpStatus":201,"purgeId":"edcp-NZbXzFpHBjcJeryhw6PVgG","supportId":"edcp-NZbXzFpHBjcJeryhw6PVgG"}