Rate and resource limiting

Property Manager API (PAPI) imposes various limits on some of the resources you can deploy. In some cases, you may have the option to override these limits. Contact your Akamai representative for more information.

Various responses include HTTP headers that provide details on your current limits:

Custom headers suffixed *-Limit report on the overall limit.
Corresponding headers suffixed *-Remaining tell you how many items you have left to deploy.
For activations, an additional *-Reset header lets you know when the current *-Remaining value rises to the original *-Limit value.

PAPI rate limits

Limit	Default Value	Description
`X-RateLimit-Limit`	100	Maximum sustainable number of request allowed each minute per account. This rate limit protects PAPI resources from being exhausted by single users. Once you exceed the limit, you receive the 429 error. If you call PAPI using multiple API clients within the same account, the rate limit applies globally to all API clients. This API also provides a burst limit that specifies how many requests you can make in excess of the imposed rate limit. The one-time burst limit is 1000 requests. Once you consume all available resources, the burst capacity increases steadily by 100 requests every minute, until it reaches its initial maximum limit of 1000.

PAPI resource limits

Limit	Default Value	Description
`X-Limit-Clientip-Per-Include-Limit`	10	Maximum number of separate Client IP matches per include.
`X-Limit-Clientip-Per-Property-Limit`	10	Maximum number of separate Client IP matches per property rule tree configuration.
`X-Limit-Max-Clientip-Per-Match-Limit`	300	Maximum number of separate IP addresses allowed within each Client IP match.
`X-Limit-Max-Cpcodes-Limit`	100	Maximum number of CP Codes created in PAPI per account. CP codes have high water-mark limits that can be overridden upon request. This header applies to users without any custom overrides. For more details, see Rate and resource limiting in the CP Codes and Reporting Groups API.
`X-Limit-Cpcodes-Per-Account-Limit`	100	Maximum number of CP Codes created in PAPI per contract. CP codes have high water-mark limits that can be overridden upon request. This header applies to users who have an override set on the account level. For more details, see Rate and resource limiting in the CP Codes and Reporting Groups API.
`X-Limit-Cpcodes-Per-Contract-Limit`	100	Maximum number of CP Codes created in PAPI per account. CP codes have high water-mark limits that can be overridden upon request. This header applies to users who have an override set on the contract level. For more details, see Rate and resource limiting in the CP Codes and Reporting Groups API.
`X-Limit-Default-Certs-Per-Contract-Limit`	Dynamic, the limit depends on the contract terms	Maximum number of hostnames with Default DV certificates per contract. This limit applies only if you have hostnames with Default DV certificates assigned to a property version. Most customers use a single contract.
`X-Limit-Edgehostnames-Per-Contract-Limit`	1000	Maximum number of edge hostnames per contract. Most customers use a single contract.
`X-Limit-Elements-Per-Include-Limit`	30	Maximum number of separate matches and behaviors per include.
`X-Limit-Elements-Per-Property-Limit`	3000	Maximum number of separate matches and behaviors per property rule tree configuration.
`X-Limit-Hosts-Per-Account-Limit`	10 000	Maximum number of hostnames you can assign to all hostname bucket properties under an account. For now, once you reach that limit, contact Akamai services to have it raised.
`X-Limit-Hosts-Per-Property-Limit`	1000 for traditional properties, 100 000 for hostname bucket properties	Maximum number of hostnames you can assign to a property configuration.
`X-Limit-Includes-Per-Contract-Limit`	500	Maximum number of activated include configurations per contract. Most customers use a single contract.
`X-Limit-Max-Includes-At-Default-Rule-Limit`	3	Maximum number of includes nested in a property's default or blank rule. See Rule trees for details on how rules work.
`X-Limit-Matched-Includes-Per-Property-Limit`	300	Maximum number of activated `MICROSERVICES` includes per parent property.
`X-Limit-Max-Nested-Rules-Limit`	6	Maximum number of nested child rules in a property to apply conditional logic. See Rule trees for details on how nested rules work.
`X-Limit-Max-Nested-Rules-Per-Include-Limit`	4	Maximum number of nested child rules in an include to apply conditional logic. See Rule trees for details on how nested rules work.
`X-Limit-Max-Parent-Property-References-Per-Include-Limit`	3000	Maximum number of activated parent properties where a single include is referenced.
`X-Limit-Properties-Per-Contract-Limit`	1000	Maximum number of activated property configurations per contract. Most customers use a single contract.
`X-RateLimit-Activations-Limit`	500	Maximum number of PAPI configurations you can activate each day on either staging or production networks.

Once you reach the limit, the API responds with a 429 error.

PAPI configuration limits

Some of the limits apply to both the Property Manager UI as well as PAPI, and some only apply to PAPI. The special limits for PAPI are mostly there to protect against situations such as runaway scripts. But be aware that this difference in limits can lead to issues: for example, if you create or edit a configuration with the Property Manager UI and then use PAPI to edit or activate the configuration, PAPI may enforce some limits that the Property Manager UI does not.

Limit	Default Value	Description
Nested Rules	6	Property Manager Rules can be nested together to form complex if/then constructs. This particular limit sets a maximum number of if/then sub-rules you can have, for instance: Rule: If file extension = jpg thenSub Rule 1: If cookie 'foo' = bar thenSub Rule 2: If country = US thenetc (up to the maximum nested rules limit)
Hostnames per Property/Config	1000	The maximum number of hostnames you can add to a Property Manager configuration.
Elements per Property/Config	3000	The maximum number of matches and behaviors in a Property Manager config.
Client IP Matches per Property/Config	10	The maximum number of separate Client IP Matches in a Property Manager config.
IP Addresses per Client IP Match	300	Maximum number of IP addresses within a single Client IP Match in a Property Manager config.
Property Manager Configs per Contract	1000	Maximum number of activated Property Manager configs per contract (most customers have just one contract).
Edge Hostnames per Contract	1000	Maximum number of Edge Hostnames created via PAPI per contract (most customers have just one contract).
Property Manager activations per rolling 24-hour window	100	Max number of Property Manager configs activated via PAPI on either staging or production over a rolling 24-hour window.
PAPI Burst Rate Limit	16	Maximum number of PAPI requests per second over a five-second interval from a single IP address. Note that multiple PAPI clients from behind a corporate firewall will appear as a single IP address. You will get a 403 deny error if you exceed the limit. If you exceed this limit you will be in a penalty box for 10 minutes. Continuing to exceed the limit will extend the time you are in the penalty box.
PAPI Average Rate Limit	12	Maximum number of PAPI requests per second over a two-minute interval from a single IP address. Note that multiple PAPI clients from behind a corporate firewall will appear as a single IP address. If you exceed this limit you will be in a penalty box for 10 minutes. Continuing to exceed the limit will extend the time you are in the penalty box. You will get a 403 deny error if you exceed the limit.