Quick answer
AWS API Gateway documents request payload as 10 MB. The payload quota is documented as non-increasable.
Verified Aug 22, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| request payloadThe payload quota is documented as non-increasable. | 10 MB | HTTP APIs | Amazon Web ServicesAug 22, 2026 |
Why does this limit matter?
A Lambda function's own payload ceiling can be lower than the gateway's, so the smallest link wins.
This value is scoped to HTTP APIs; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Measure transmitted request bytes and compare every integration hop, not only API Gateway.
- Confirm the exact plan, model, runtime, endpoint, region, and account that serve the failing workload.
- Record the observed value, response headers or configuration, timestamp, and source without logging secrets.
Important caveats
- Header size and access-log entry size are separate constraints.
- Treat the official source and live account configuration as authoritative if they differ from this verified snapshot.
HyperObserve reports the documented platform constraint. Your application, SDK, gateway, provider, region, or account can impose a lower effective limit.
Related