Limits

This page applies to Apigeeand Apigee hybrid.

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.

Some limits differ between Apigee and Apigee hybrid. The limits can also differ based on your Apigee subscription type. If you are using Apigee hybrid, the higher limits enabled by Subscription 2024 require a newly provisioned using hybrid version 1.14. or later. See Enhanced per-environment proxy limits for details.

Feature area

Limit

Apigee
Currently enforced?

Apigee hybrid
Currently enforced?

Apigee APIs

User, service account, or Apigee UI initiated

6,000 per minute

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

API Proxies

API proxy or shared flow zip file bundle size

15 MB

Yes

API proxy revisions retained in history

250

Yes

API proxy shared flow revisions retained in history

250

Yes

API proxy resource files size (such as XSL, JavaScript, Python, or JAR files).

15 MB

Yes

Deployed API proxies and shared flows per organization

Apigee : 6000

Apigee hybrid : 4,250 (Subscription 2021)

Apigee hybrid : 6,000 (Subscription 2024)

Pay-as-you-go : varies

Yes

Deployed proxies per environment

Apigee : 6,000

Apigee hybrid : 50
(Subscription 2021)

Apigee hybrid : 6,000 (Subscription 2024)

Pay-as-you-go : varies

Yes

Deployed shared flows per environment

Apigee : 75

Apigee hybrid : 10
(Subscription 2021)

Apigee hybrid : 75
(Subscription 2024)

Pay-as-you-go : varies

Yes

Proxy Deployment Units ( PDUs ) per instance

6,000

Yes

API proxy endpoints per API proxy

Check usage:
/apis/revisions
examine proxy bundle

Yes

Environment-scoped resource files per environment

100

Yes

Quota

Distributed quota synchronization interval

>= 10 seconds

Yes

Planned

Max Quota Interval

1 year

Planned

Min Quota Interval

1 minute

Planned

SpikeArrest

Rate

Per second maximum: 4,000
Per minute maximum: 240,000

Planned

Persistence: Cache, KVM, Property sets

Caches at the environment scope

100

Planned

Cache key size

2 KB

Yes

Planned

Cache value size

256 KB

Yes

Planned

Cache expiration

>=1 second, <= 30 days

Yes

Cache resource deletion rate

1 per minute

Yes

Planned

Items in cache

10 million in each cache

Planned

Items in KVMs across all KVMs in the organization

5 million

Planned

Key Value Maps (KVMs) at the organization scope

100

Planned

Yes

Key Value Maps (KVMs) at the environment scope

900

Planned

Key Value Maps (KVMs) at the proxy scope

4,250 or 6,000 (the maximum number of API proxies that can be deployed in an organization)

Planned

Key Value Map (KVM) key size

2 KB

Planned

Key Value Map (KVM) value size

10 KB

Planned

Environment-scoped property sets per environment

Planned

Proxy-scoped property sets per environment

Planned

Size of property set file

110 KB

Planned

Keys, Developers, Apps

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

Yes

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

Planned

Apps per developer

100

Planned

Apps per organization

1 million

Planned

Yes

Apps per AppGroup

30,000

Planned

AppGroups per organization

1 million

Planned

API products per API Key

Planned

API products per app

100

Planned

API products per organization

5,000

Planned

Yes

API Products

API Resources > Proxies

100

Planned

API Resources > Paths

Planned

REST and GraphQL Operations

Yes

Environments

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

Planned

External OAuth access token size

2 KB

Yes

Planned

Custom attributes you can set on OAuth tokens

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 85, but depends on contract
Apigee hybrid: 85

Yes

Environment groups per organization

Apigee: Up to 85
Apigee hybrid: 85

Yes

Environment group attachments per org

100

Yes

Instances per organization

10 (11 for hybrid)

Yes

Planned

Instances per region

Yes

N/A

Regions per organization

10 (11 for hybrid)

Yes

N/A

API base paths per organization

Note: See BasePath in ProxyEndpoint configuration elements for information on base paths.

6,000

Yes

Hostnames per environment group

100

Yes

Aliases per key

100

Yes

Developer portals per organization

Yes

Developer accounts per portal

800 K

Planned

Key stores per environment

100

Yes

Kubernetes clusters per org

N/A

Planned

Orgs per Cassandra cluster

N/A

Planned

Target servers per environment

1,000

Planned

Trust stores per environment

1,000

Yes

Portals

Maximum pages per portal

1,000

Yes

Maximum published APIs or API products per portal

1,200

Yes

Maximum API documentation size for a published API

4 MB

Yes

Maximum API categories per portal

200

Yes

Maximum menu items per portal

200

Yes

Maximum files per portal

500

Yes

Maximum file size

10 MB

Yes

Maximum file storage usage

100 MB

Yes

Maximum audiences per portal

Yes

Maximum developer accounts per audience

800 K (max users)

Planned

Maximum developer teams per audience

200 K

Yes

Developer teams per portal

200 K

Planned

Maximum developer teams a developer can be a member of

Yes

Maximum members in a developer team

100

Yes

Maximum characters in a portal's Custom Scripts JavaScript field

150,000

Yes

Private Service Connect (PSC)

PSC Network Endpoint Groups (NEGs) for northbound connections

As of October 10, 2024, Apigee does not limit the number of Cloud projects that can connect to an Apigee instance through PSC; however, Google Cloud private service connect quota limits apply. Previously, the limit was 50 projects. For each project, you can now create up to 100 PSC NEGs. The previous limit was 20. For any Apigee instances created before October 10, 2024, you must update the consumer accept list for an Apigee instance if you want to take advantage of these new limits.

If you need to have more than 1000 PSC NEG connections in total across all of the Cloud projects connected to an Apigee instance, contact Google Cloud Support .

Yes

N/A

Endpoint attachments per organization for southbound connections

1,000

Yes

N/A

DNS peering

Number of peering zones per Apigee organization

1000
This limit is a constraint imposed on Apigee by Cloud DNS. For details, see Resource limits .
Note: This limit applies only for Apigee organizations without VPC peering.

N/A

System

Target connection timeout

300 seconds

Planned

API proxy request URL size

10 KB

Yes

Request header size

60 KB

Yes

Response header size

60 KB

Yes

Request/response size for buffered (non-streamed) requests

30 MB

Yes

Request/response size for streamed requests

When streaming is enabled, payloads greater than 10 MB are allowed; however, there could be performance implications.

10 MB

TLS / DTLS maximum handshake message size

128 KB

Yes

Target endpoints per proxy

1,000

Yes

Debug Sessions

Maximum debug sessions

You can create at most 100 debug sessions per minute per project

Yes

Maximum debug transactions per session

Yes

Debug payload (per transaction)

No limit

Yes

Maximum configurable sampling rate for distributed tracing

0.5

Yes

Maximum debug data size

Payloads, headers, and flow variables are truncated.

10 KB

Yes

Analytics APIs

Maximum time range that can be queried via synchronous report

14 days for hybrid and 92 days for Apigee

Asyncronous queries enforce a 365 day maximum

Yes

Calls to the Analytics Metrics API

100 calls per minute

Yes

Calls to the Asynchronous Query API

300 calls per day

Yes

Calls to the Data Export API

500 calls per day

Yes

API Monitoring

Data retention period

6 weeks

Yes

Maximum latency observed

60 seconds

Yes

Pay-as-you-go

Max Base environments per org

Yes

N/A

Max Intermediate environments per org

Yes

N/A

Max Comprehensive environments per org

Yes

N/A

Max proxy deployments per Base environment per region

Yes

N/A

Max proxy deployments per Intermediate environment per region

Yes

N/A

Max proxy deployments per Comprehensive environment per region

100 included

Ability to purchase up to 6000

Yes

N/A

Max shared flow deployments , subject to restrictions per environment type

Yes

N/A

Apigee Spaces

Max number of Apigee Spaces per organization

Yes

Max number of queries per second (QPS) for list operations for API proxy, API product, and shared flow endpoints

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.