Akamai Technologies · Rate Limits
Akamai Technologies Rate Limits
Akamai is a multi-service platform; API rate limits vary by product surface. Control-plane APIs (Akamai EdgeGrid OPEN APIs covering CDN configuration, Property Manager, Cloud Computing, EdgeWorkers, Security configuration, Reporting, Identity, etc.) each have service-specific throttles. Akamai Cloud Computing inherits the published Linode API rate limits. Throttling responses follow standard 429 / Retry-After conventions; specific numeric limits are documented in per-service Akamai TechDocs / API reference pages.
3 Limits
Throttle: 429
CDNEdgeCloudSecurityRate Limiting
Limits
EdgeGrid Control-Plane APIs api_client
service-specific TPS / RPM, see per-API TechDocs
Property Manager, Cloud Computing, Security Configuration, Reporting, etc. each publish their own rate-limit ceilings; EdgeGrid signing is required.
Cloud Computing (Linode) API account
see Linode API rate-limit documentation
Linode API publishes documented per-endpoint limits and uses the X-RateLimit-* family of headers.
CDN edge request volume account
governed by contract (committed traffic / requests / RPS), not a public number
Policies
Backoff Strategy
Clients should implement exponential backoff with jitter on 429 / 503 responses, honoring Retry-After when present.
EdgeGrid Authentication
Akamai control-plane APIs require EdgeGrid request signing; misconfigured clients can be blocked before reaching rate limits.
Per-Service Limits
Numeric limits are published per API in TechDocs. Treat them as authoritative — do not infer one product's limits from another.
Contract-Governed CDN Capacity
CDN traffic capacity is contractual, not an API rate limit. Coordinate with the Akamai account team before unusual traffic events.