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 theCurrently 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. SeeEnhanced per-environment proxy limitsfor 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
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 revisionsretained in history
250
Yes
Yes
API proxy shared flow revisionsretained in history
250
Yes
Yes
API proxyresource filessize(such as XSL,
JavaScript, Python, or JAR files).
15 MB
Yes
Yes
Deployed API proxies and shared flows per organization
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 Cloudprivate service connect quota limitsapply. 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 mustupdate the consumer accept list for an Apigee instanceif 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, contactGoogle Cloud Support.
1000 This limit is a constraint imposed on Apigee by Cloud DNS. For details, seeResource limits. Note: This limit
applies only for Apigee organizations without VPC peering.
N/A
N/A
System
Target connection timeout
300 seconds
Planned
Planned
API proxy request URL size
10 KB
Yes
Yes
Request header size
60 KB
Yes
Yes
Response header size
60 KB
Yes
Yes
Request/response size for buffered (non-streamed) requests
Max proxy deployments
per Base environment per region
20
Yes
N/A
Max proxy deployments
per Intermediate environment per region
50
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
75
Yes
N/A
Apigee Spaces
Max number of Apigee Spaces per organization
20
Yes
Yes
Max number of queries per second (QPS) forlistoperations for API proxy, API product, and shared flow endpoints
10
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.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[[["\u003cp\u003eApigee and Apigee hybrid have specific configuration limits that are crucial for maintaining stability and performance, with exceeding these limits potentially leading to issues like high latency and call failures.\u003c/p\u003e\n"],["\u003cp\u003eLimits vary across different feature areas including API calls, message logging, API proxies, quotas, SpikeArrest, persistence, keys, developers, apps, environments, OAuth, portals, Private Service Connect, system operations, and debug sessions.\u003c/p\u003e\n"],["\u003cp\u003eAPI Proxy configuration limitations include bundle sizes of 15 MB, retaining 250 revisions, 10 endpoints per proxy, and varying numbers of deployed proxies and shared flows depending on the subscription type, and other values.\u003c/p\u003e\n"],["\u003cp\u003ePersistence limitations, such as cache and KVMs, restrict cache key sizes to 2 KB, cache value sizes to 256 KB, and items in caches to 10 million, as well as several KVM limitations.\u003c/p\u003e\n"],["\u003cp\u003eThere are several limitations surrounding Apigee's API developer portals including limits to the maximums for pages, published APIs, API Categories, menu items, files, file sizes, audiences, developer teams, and custom scripts.\u003c/p\u003e\n"]]],[],null,["# Limits\n\n*This page\napplies to **Apigee** and **Apigee hybrid**.*\n\n\n*View [Apigee Edge](https://docs.apigee.com/api-platform/get-started/what-apigee-edge) documentation.*\n\nConsider the following product configuration limits as you build, manage, and review\nyour API program implementation. We've designed the Apigee product for stability and performance\nwhen configured within these limits. Customers are responsible for tracking\nand ensuring they stay within the configuration limits. Customers exceeding the limits may\nexperience one or more of these types of symptoms: high API latencies, low API throughput,\nand failing API calls. Customers filing support cases related to issues caused by limit\nexceptions may be asked to make necessary modifications to their configuration.\n\nLimits may or may not be enforced automatically (see the **Currently enforced?** column below).\nAs and when we automate limit enforcement for a limit currently not enforced, we will use\ncommercially reasonable efforts to notify affected customers so they can take corrective\nactions in advance of such enforcement.\n\nSome limits differ between Apigee and Apigee hybrid. The limits can\nalso differ based on your Apigee subscription type. If you are using Apigee hybrid, the higher\nlimits enabled by Subscription 2024 require a newly provisioned using hybrid version 1.14. or later. See\n[Enhanced per-environment proxy limits](/apigee/docs/hybrid/v1.14/enhanced-proxy-limits) for details.\n| **Note:** This page describes *technical configuration limits* . Enforced limits are fixed and cannot be changed or increased for individual organizations or environments. Organization entitlement terms apply to all usage; exceeding entitlement limits can increase costs, even if usage is within the limits described on this page. See [Apigee Pricing](https://cloud.google.com/apigee/pricing) for details and pricing options.\n\n\n**The information above represents current product limits. Google reserves the right to\nchange product features and functionality or the above limits upon posting or otherwise making them\naccessible.**"]]
