Limits

You're viewing Apigee X documentation.
View Apigee Edge documentation.

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. 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 Apigee
Currently enforced?
Apigee hybrid
Currently enforced?

Apigee APIs

User, service account, or Apigee UI initiated 6,000 per minute Yes Yes
Invoked by synchronizer 1,000 per minute N/A Yes
Invoked by UDCA 6,000 per minute N/A Yes

Message logging

Message logging payload 11 MB Planned Planned

API Proxies

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

Check usage:
/apis/revisions
examine proxy bundle

5 Yes Yes
Resources per environment 100 Yes Yes

Quota

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

Persistence: Cache, KVM, Property sets

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

Keys, Developers, Apps, Products

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

OAuth

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

Environment and Organization

Environments per organization Apigee: Up to 75, but depends on contract
Apigee hybrid: 75
Yes Yes
Environment groups per organization Apigee: Up to 75
Apigee hybrid: 75
Yes Yes
Instances per org 5 Yes Yes
Instances per region 1 Yes Yes
Environments per region Depends on the number of allocated IP addresses in the Customer VPC peering network:
  • /16 CIDR block: 75 environments
  • /20 CIDR block: 14 environments
Yes N/A
Regions per organization 5 Yes N/A
Hostnames per environment group 100 Yes Yes
Aliases per key 100 Yes Yes
Developer portals per organization 100 Planned Yes

Developer accounts per portal

800 K Planned Planned
Developer teams per portal 200 K Planned Planned
Maximum developer teams a developer can be a member of 64 Yes Yes
Maximum members in a developer team 100 Planned Planned
Key stores per environment 100 Yes Yes

API calls for all environments (in a region)

8,400 to 11,200 Yes N/A
Kubernetes clusters per org 5 Planned Planned
Orgs per Cassandra cluster 5 Planned Planned
Target servers per environment 1,000 Planned Planned
Trust stores per environment 1,000 Yes Yes

Portals

Maximum pages per portal 1,000 Yes Yes
Maximum published APIs or API products per portal 1,000
500
Planned
Yes
Planned
Yes
Maximum API categories per portal 200 Yes Yes
Maximum menu items per portal 200
100
Planned
Yes
Planned
Yes
Maximum files per portal 500 Yes Yes
Maximum audiences per portal 16 Yes Yes
Maximum developer accounts per audience 800 K (max users) Planned Planned
Maximum developer teams per audience 200 K
100 K
Planned
Yes
Planned
Yes

System

Target connection timeout 600 seconds Planned Planned
API proxy request URL size 7 KB Yes Yes
Request header size 30 KB Yes Yes
Response header size 25 KB Yes 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

Non-streamed: Yes

Streamed: No

Planned
TLS / DTLS maximum handshake message size 128 KB (131072 bytes) Yes Yes

Debug Sessions

Trace sessions 100 creation API calls per minute per project Yes Yes
Trace transactions per session 15 using UI,
Default = 10 per Message Processor using API
Yes Yes
Trace payload (per transaction) No limit Yes Yes

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

Maximum time range that can be queried via synchronous report

14 days

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

70 calls per month

10 concurrently running export jobs

Yes 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.