Limits

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 Apigee and another set applies to Apigee hybrid. These limits are unrelated to your Apigee Pricing.

Feature area Limit Currently enforced?

Apigee APIs

User, service account, or Apigee UI initiated 6000 per minute Yes
Invoked by synchronizer (hybrid only) 1000 per minute Yes
Invoked by UDCA (hybrid only) 6000 per minute Yes

Message logging

Message logging payload 11 MB Planned

API Proxies

API proxy or shared flow zip file bundle size 15 MB Yes
API proxy revisions retained in history 1000 Yes
API proxy resource file size (such as XSL, JavaScript, Python, or JAR files). 15 MB Yes
Number of deployed API proxies plus shared flows per environment (combined) 50 Yes
Number of API proxy endpoints

Check usage:
/apis/revisions
examine proxy bundle

5 Yes
Number of resources per environment 100 Yes

Quota

Distributed quota synchronization interval >= 10 seconds Yes
Max Quota Interval 1 month Planned
Min Quota Interval 1 minute Planned

Persistence: Cache, KVM, Property sets

Caches at the environment scope 100 Planned
Cache key size 2 KB Yes
Cache value size 512 KB Yes
Cache expiration >=1 second, <= 30 days Planned
Cache resource deletion rate 1 per minute Yes
Items in cache 10 million in each cache Planned
Items in KVMs 5MM Planned
Key Value Maps (KVMs) at the organization scope 100 Planned
Key Value Maps (KVMs) at the environment scope 100 Planned
Key Value Maps (KVMs) at the proxy scope 100 Planned
Key Value Map (KVM) key size 2 KB Planned
Key Value Map (KVM) value size 10 KB Planned
Number of environment-scoped property sets per environment 10 Planned
Number of proxy-scoped property sets per environment 50 Planned
Size of each property name (key) in a property set 100 Bytes Planned
Size of property set file (100 + 1024) * 100 = ~110KB Planned

Keys, Developers, Apps, Products

Consumer key (API key) size 2 KB Yes
Consumer secret size 2 KB Yes
Custom attributes you can set on developers, developer apps, API products, OAuth access tokens, and other Apigee entities 18 Yes
Custom attribute name size 1 KB Yes
Custom attribute value size 2 KB Yes
Developers per organization 1 million Planned
Number of API Keys per app 10 Planned
Number of apps per developer 10 Planned
Number of apps per organization 1 million Planned
Number of environments per product 25 Planned
Number of products per API Key 50 Planned
Number of products per app 100 Planned
Number of products per organization 5000 Planned
Number of proxies per product 25 Planned

OAuth

OAuth access token expiration >= 180 seconds, <= 30 days Yes
OAuth refresh token expiration >= 1 day, <= 2 years Yes
OAuth access and refresh token size 2 KB Yes
Custom attributes you can set on OAuth tokens 18 Yes
Custom attribute name size 1 KB Yes
Custom attribute value size 2 KB Yes

Environment and Organization

Environments per organization Apigee: Up to 75, but depends on contract
Apigee hybrid: 75
Yes
Environment groups per organization Apigee: Up to 75, but depends on your contract
Apigee hybrid: 75
Yes
Hostnames per environment group 100 Yes
Aliases per key 100 Yes
Developer portals per organization 10 Planned
Key stores per environment 100 Yes
Apigee API calls 6,000 calls per minute Yes
Number of Kubernetes clusters per org 5 Planned
Number of orgs per Cassandra cluster 5 Planned
Target Servers per environment 1000 Planned
Trust stores per environment 1000 Yes
Virtual hosts per environment Customer managed No

System

Target connection timeout 600 seconds Planned
API proxy request URL size 7 KB Yes
Request header size 30 KB Yes
Response header size 25 KB Yes

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 Cloud Storage provide reference implementations using this pattern.

10 MB

Yes for non-streamed

No for streamed

Analytics APIs (API calls only; not enforced for UI usage)

Maximum time range that can be queried via synchronous report

14 days

Planned
Calls to the Asynchronous Query API per environment 7 calls per hour No
Calls to the Data Export API per environment

70 calls per month

10 concurrently running export jobs

Yes

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.