Quotas and limits in API Gateway
Written by
Updated at May 13, 2026
API Gateway has the following limits:
- Quotas are organizational constraints that can be changed by contacting technical support.
- Limits are technical constraints of the Yandex Cloud architecture. You cannot change the limits.
If you need more resources, you can increase your quotas in one of the following ways:
- Make a request to increase your quotas.
- Contact support and specify which quotas you want increased and by how much.
To have your request processed, you must have the quota-manager.requestOperator role or higher, e.g., editor or admin.
You can manage your quotas with Cloud Quota Manager.
Quotas
|
Type of limit |
Value |
|
Number of triggers per cloud1 |
100 |
|
Number of user networks per cloud |
10 |
1 API Gateway, Cloud Functions, and Serverless Containers share the same Number of triggers per cloud quota. The management console shows it as part of the Cloud Functions quota list.
Limits
| Type of limit | Value |
|---|---|
| Maximum size of a request to and a response from API Gateway | 2.5 MB |
| Maximum specification size | 3.5 MB |
| Maximum request processing timeout | 10 minutes1 |
| Maximum size of message being transmitted via a web socket | 128 KB |
| Maximum size of frame being transmitted via a web socket | 32 KB |
| Maximum time-to-live of a web socket connection | 60 minutes |
| Maximum time-to-live of an idle web socket connection | 10 minutes |
| Maximum number of triggers per message queue | 1 |
| Maximum message size per trigger2 | 230 KB |
| Maximum number of domains you can connect to a single API gateway | 20 |
1 Default value: 5 minutes.
2 The message may include service metadata, which will reduce the maximum message size.