Blog

PAPI Quota Limits

The Official List of PAPI Quota Limits

March 13, 2018 · by Jay Sikkeland ·
Categories:

Property Manager and its corresponding Open API (which we call "PAPI" for short because it's the Property Manager API) are powerful tools to manage the way your web content is delivered on the Akamai platform. Using Property Manager and PAPI's nested rules with matches and behaviors, you can do almost anything.

Please note that I said "almost anything." In order to protect the Akamai platform and customers like you from inadvertent situations, we created certain quota limits for these tools. I thought it might be helpful for you to know exactly what those limits are, and so they’re all listed below for your reference.

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.

Most of these limits can be increased in special circumstances. If you have use cases that require higher limits now or in the future, please reach out to your account team with details and we can often accommodate your request.

So, without further ado, here is a list of these limits, what they mean, and where they apply:

 

 

LimitDefault ValueDescriptionApplies ToNotes
Nested Rules6Property 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 then

Sub Rule 1:  If cookie 'foo' = bar then

Sub Rule 2:  If country = US then

etc (up to the maximum nested rules limit)

PM UI

PAPI

 
Hostnames per Property/Config1000The maximum number of hostnames you can add to a Property Manager configuration.PM UI

 

PAPI

The performance of the Property Manager UI and PAPI validation checks degrade as you add more hostnames.  We therefore typically recommend no more than 300 hostnames per Property Manager config, although this depends on the complexity of the rest of your configuration.

 

To improve the validation performance in the Property Manager UI, you can check the "Disable Auto Validate" checkbox in the Errors and Warnings tab at the bottom of the edit window.

To improve PAPI validation performance you can include the validateRules=false and validateHostnames=false query parameters - See the PAPI docs for details.

Elements per Property/Config1500The maximum number of matches and behaviors in a Property Manager config.PAPITo prevent a PAPI script/app from accidentally generating a huge Property Manager config.
Client IP Matches per Property/Config10The maximum number of separate Client IP Matches in a Property Manager config.PAPI 
IP Addresses per Client IP Match300Maximum number of IP addresses within a single Client IP Match in a Property Manager config.PAPI 
Property Manager Configs per Contract1000Maximum number of activated Property Manager configs per contract (most customers have just one contract).PAPIThis protects against a PAPI script/app creating and activating millions of Property Manager configs.
Edge Hostnames per Contract1000Maximum number of Edge Hostnames created via PAPI per contract (most customers have just one contract).PAPITo prevent a PAPI script/app from creating millions of Edge Hostnames.
Property Manager activations per rolling 24-hour window100Max number of Property Manager configs activated via PAPI on either staging or production over a rolling 24-hour window.PAPIProtects against a PAPI script/app activating too many Property Manager configs.
CP Codes created per contract per day20Maximum number of CP Codes created via PAPI per contract per day (most customers have just one contract).PAPIThis limit will soon be replaced by a high-water-mark limit; that means you can have up to a certain number of CP codes but we won't limit how fast you create them.
PAPI Burst Rate Limit16Maximum 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.

>> Note that you will get a 403 deny error if you exceed the limit.

>> Note that 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.

PAPIWe are planning on providing higher (and more fine-grained) rate limits in the near future.
PAPI Average Rate Limit12Maximum 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.

>> Note that 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.

>> Note that you will get a 403 deny error if you exceed the limit.

PAPIWe are planning on providing higher (and more fine-grained) rate limits in the near future.

 

For more details on PAPI, see the PAPI home page.

For specific details on PAPI’s rate and resource limiting, go here.

We also have lots of great blog posts, presentations, and how-to guides on PAPI. Browse the list here.

Jay Sikkeland is a senior product manager at Akamai Technologies.