You're viewing Apigee Edge documentation.
Go to the
Apigee X documentation. info
Consider the following product configuration limits as you build, manage, and review your API program implementation. We’ve designed the Apigee product for stability and performance when configured within these limits. Customers are responsible for tracking and ensuring they stay within the configuration limits (see the "How to check current usage" column below). Customers exceeding the limits may experience one or more of these types of symptoms: high API latencies, low API throughput, and failing API calls. Customers filing support cases related to issues caused by limit exceptions may be asked to make necessary modifications to their configuration.
Limits may or may not be enforced automatically (see the "Currently enforced?" column below). As and when we automate limit enforcement for a limit currently not enforced, we will use commercially reasonable efforts to notify affected customers so they can take corrective actions in advance of such enforcement.
One set of configuration limits apply to both Apigee Public Cloud and Private Cloud (on-premises) products, and another set applies to Edge Microgateway. These limits are unrelated to your plan entitlements. Some features, noted in this topic, are available only in Apigee Public Cloud.
Cloud/Private Cloud
| Feature area | Limit | Currently enforced? | How to check current usage |
|---|---|---|---|
API Proxies |
|||
| API proxy or shared flow zip file bundle size (proxies other than Hosted Targets and Node.js) | 15 MB | Yes | Check usage |
Hosted Targets bundle size Hosted Targets are currently available only in Apigee Public Cloud. |
250 MB | Planned | Check usage |
Hosted Targets |
The Hosted Targets
feature is a plan entitlement. |
||
| API proxy revisions retained in history | 50 | Planned | Check usage |
| API proxy resource file size (such as XSL, JavaScript, Python, or JAR files). Doesn't include Hosted Targets resources. | 15 MB | Yes | Check usage |
Extensions |
|||
| Extensions queries | 120 requests per second to each extension | Planned | N/A |
| Extensions response payload | 2 MB | Planned | N/A |
Quota |
|||
| Distributed quota synchronization interval | >= 10 seconds | Yes | Check usage |
Persistence: Cache, KVM |
|||
| Caches at the environment scope | 100 | Planned | Check usage |
| Items in cache | 2.5 million items in each cache | Planned | Planned |
| Cache key size | 2 KB | Yes | Check usage |
| Cache value size | 256 KB | Yes | Check usage |
| Cache expiration | >=180 seconds, <= 30 days | Planned | Check usage |
| Key Value Maps (KVMs) at the organization scope | 100 | Planned | Check usage |
| Key Value Maps (KVMs) at the environment scope | 100 | Planned | Check usage |
| Key Value Maps (KVMs) at the proxy scope | 100 shared across all API proxies defined in a given organization | Planned | Check usage |
| Items in KVMs | 5 million total items in all KVMs at all scopes in an organization | Planned | Check usage: organization environment API proxy API proxy revision |
| Key Value Map (KVM) key size* | 2 KB | Yes | Check usage: organization environment API proxy API proxy revision |
| Key Value Map (KVM) value size* | 10 KB | Planned | Check usage |
|
* For Apigee Edge for Private Cloud, the combined size of the keys and values should not exceed 15MB per KVM. To determine the size of your KVMs, you can use the nodetool cfstats command. |
|||
Keys, Developers, Apps, Products |
|||
| Consumer key (API key) size | 2 KB | Yes | Check usage |
| Consumer secret size | 2 KB | Yes | Check usage |
| Custom attributes you can set on developers, developer apps, API products, OAuth access tokens, and other Edge entities | 18 | Yes | Check usage: Developers Developer apps API products Access tokens |
| Custom attribute name size | 1 KB | Yes | Check usage: Developers Developer apps API products Access tokens |
| Custom attribute value size | 2 KB | Yes | Check usage: Developers Developer apps API products Access tokens |
| Developers per organization | 1 million | Planned | Check usage |
OAuth |
|||
| OAuth access token expiration | >= 180 seconds, <= 30 days | Yes | Check usage |
| OAuth refresh token expiration | >= 1 day, <= 2 years | Yes | N/A |
| OAuth access and refresh token size | 2 KB | Yes | Check usage |
| Custom attributes you can set on OAuth tokens | 18 | Yes | Check usage |
| Custom attribute name size | 1 KB | Yes | Check usage |
| Custom attribute value size | 2 KB | Yes | Check usage |
Environment and Organization |
|||
| Developer portals per organization | 10 | Planned | Planned |
| Evaluation organizations | Deleted after 60 days. Also see the Google Terms of Service for Apigee Products for evaluation accounts. | Yes | Banner in product UI |
| Management API calls |
|
Yes | Planned |
| Target Servers per environment | 500 | Planned | Check usage |
| Virtual hosts per environment | 20 | Planned | Check usage |
| TLS certificates per environment | 100 | Planned | Check usage |
| Keystores per environment | 100 | Planned | Check usage |
| Truststores per environment | 1000 | Planned | Check usage |
Portals |
|||
| Maximum pages per portal | 1,000 | Yes | N/A |
| Maximum published APIs or API products per portal | 1,200 | Yes | N/A |
| Maximum API documentation size for a published API | 4 MB | Yes | Yes |
| Maximum API categories per portal | 200 | Yes | N/A |
| Maximum menu items per portal | 200 | Yes | N/A |
| Maximum files per portal | 500 | Yes | N/A |
| Maximum file size | 10 MB | Yes | N/A |
| Maximum file storage usage | 100 MB | Yes | N/A |
| Maximum audiences per portal | 16 | Yes | N/A |
| Maximum developer accounts per audience | 800 K (max users) | Planned | N/A |
| Maximum developer teams per audience | 200 K | Yes | N/A |
| Developer teams per portal | 200 K | Planned | N/A |
| Maximum developer teams a developer can be a member of | 64 | Yes | N/A |
| Maximum members in a developer team | 100 | Yes | N/A |
| Maximum characters in a portal's Custom Scripts JavaScript field | 150,000 | Yes | N/A |
System |
|||
| API proxy request URL size | 7 KB | Yes | Check usage |
| Request header size | 25 KB | Yes | Check usage |
| Response header size | 25 KB | Yes | Check usage |
Request/response size (for both non-streamed and streamed requests) A common API pattern is to fetch large amounts of data, such as images, documents, or plain text/JSON. For data sizes greater than 10 MB, Apigee recommends a signed URLs pattern. Other Google products like GCS (Google Cloud Storage) provide reference implementations using this pattern. |
10 MB | Yes for non-streamed No for streamed |
cURL the API proxy |
|
Request Line Limit The limit set for each line of a request header. |
7K | Yes | Check Limits |
|
Response Line Limit The limit set for each line of a response header. |
2K | Yes | Check Limits |
API Monitoring |
|||
| API Monitoring alerts | 20 | Yes | Check usage |
| API Monitoring collection items | 20 | Yes | Check usage |
| Data retention period | 55 days |
Yes | N/A |
Analytics APIs(API calls only, not enforced when using the UI) |
|||
| Calls to the Asynchronous Query API per environment (Public Cloud only) | 7 calls per hour | No | N/A |
| Calls to the Stats APIs per environment (Public Cloud only) | Postgres: 40 calls per minute BigQuery: 12 calls per minute |
No | N/A |
| Calls to the Data Export API per environment (Public Cloud only) | 70 calls per month Monetization enabled: 70 calls per month (standard data) and 70 calls per month (monetization data) |
No | N/A |
OpenAPI Specifications |
|||
| OpenAPI Specifications | 4 MB (see note below) | Yes | Check size of file on local system |
Edge Microgateway
| Feature area | Limit | Currently enforced? | How to check current usage |
|---|---|---|---|
API Proxies and Products |
|||
| Maximum number of API products returned by the edgemicro-auth proxy | 500 | No | |
| Maximum number of API proxies supported by a single instance of Edge Microgateway | 50 | No | |
System |
|||
Request/response size (for both non-streamed and streamed requests) A common API pattern is to fetch large amounts of data, such as images, documents, or plain text/JSON. For data sizes greater than 10 MB, Apigee recommends a signed URLs pattern. Other Google products like GCS (Google Cloud Storage) provide reference implementations using this pattern. |
10 MB | No |
cURL the API proxy |
| Target connection timeout | 600 seconds | No | |
For product limits for the latest Apigee and Apigee hybrid products, see Limits.
The information above represents current product limits. Google reserves the right to change product features and functionality or the above limits upon posting or otherwise making them accessible.