Amazon API Gateway Pricing
API Gateway bills each call your API receives. In us-east-1 a REST API costs $3.50 per million requests, an HTTP API $1.00, about 71% less, and WebSocket APIs charge $1.00 per million messages plus connection minutes. The rate steps down as a month's volume grows, and REST APIs can add an hourly-billed cache.
Estimate an API Gateway bill
One API's month, priced for the region you pickAPI estimator
Tier bands count one month of requests (or messages) in one region, and the estimate treats this API as the whole account's volume. REST and HTTP requests are billed on separate meters. WebSocket messages are metered in 32 KB increments, so a larger message counts as several. HTTP API requests are metered in 512 KB increments on the same reading of AWS's worked example; the pricing page does not state it as a rule, so treat it as an estimate. The price list is on-demand only. Data transfer out, PrivateLink charges for private APIs, CloudWatch, and the backend (Lambda, containers) are billed separately and are not included.
Request and message price tiers
Per-meter rates, for US East (N. Virginia)| Meter | Monthly volume | Per million | Per unit |
|---|---|---|---|
| REST API requests | First 333 million requests a month | $3.50 | $0.0000035 |
| 333 million to 1 billion requests a month | $2.80 | $0.0000028 | |
| 1 billion to 20 billion requests a month | $2.38 | $0.00000238 | |
| Over 20 billion requests a month | $1.51 | $0.00000151 | |
| HTTP API requests | First 300 million requests a month | $1.00 | $0.000001 |
| Over 300 million requests a month | $0.90 | $0.0000009 | |
| WebSocket messages | First 1 billion messages a month | $1.00 | $0.000001 |
| Over 1 billion messages a month | $0.80 | $0.0000008 | |
| WebSocket connection minutes | All connection minutes | $0.25 | $0.00000025 |
Each band's rate applies only to the requests inside it, so passing a threshold lowers the price of what comes after, not of the whole month. In us-east-1 the REST API's first 333 million requests are in the first band. Asia Pacific (Sydney), Asia Pacific (Melbourne), Asia Pacific (New Zealand), South America (Sao Paulo) publish three REST bands instead of four, with the first running to 1 billion. The table follows the region selected in the estimator.
API Gateway rates by region
36 regions. Request and message rates are first-band rates per million.| Region | REST per 1M requests | HTTP per 1M requests | WebSocket per 1M messages | WebSocket per 1M connection minutes | 10M REST requests / mo |
|---|---|---|---|---|---|
| us-east-1 US East (N. Virginia) | $3.5000 | $1.0000 | $1.0000 | $0.2500 | $35.00 |
| us-east-2 US East (Ohio) | $3.5000 | $1.0000 | $1.0000 | $0.2500 | $35.00 |
| us-west-2 US West (Oregon) | $3.5000 | $1.0000 | $1.0000 | $0.2500 | $35.00 |
| us-west-1 US West (N. California) | $3.5000 | $1.1700 | $1.2400 | $0.3100 | $35.00 |
| ca-central-1 Canada (Central) | $3.5000 | $1.1100 | $1.1000 | $0.2750 | $35.00 |
| ca-west-1 Canada West (Calgary) | $3.5000 | $1.1100 | $1.1000 | $0.2750 | $35.00 |
| eu-west-1 EU (Ireland) | $3.5000 | $1.1100 | $1.1400 | $0.2850 | $35.00 |
| eu-central-1 EU (Frankfurt) | $3.7000 | $1.2000 | $1.1400 | $0.2850 | $37.00 |
| eu-west-2 EU (London) | $3.5000 | $1.1600 | $1.1900 | $0.2970 | $35.00 |
| eu-west-3 EU (Paris) | $3.5000 | $1.1700 | $1.1900 | $0.2970 | $35.00 |
| eu-north-1 EU (Stockholm) | $3.5000 | $1.0600 | $1.0830 | $0.2710 | $35.00 |
| eu-south-1 EU (Milan) | $3.6800 | $1.1700 | $1.2000 | $0.3000 | $36.80 |
| eu-south-2 Europe (Spain) | $3.5000 | $1.1100 | $1.1400 | $0.2850 | $35.00 |
| eu-central-2 Europe (Zurich) | $4.0700 | $1.3200 | $1.2540 | $0.3135 | $40.70 |
| ap-northeast-1 Asia Pacific (Tokyo) | $4.2500 | $1.2900 | $1.2600 | $0.3150 | $42.50 |
| ap-northeast-2 Asia Pacific (Seoul) | $3.5000 | $1.2300 | $1.1400 | $0.2850 | $35.00 |
| ap-northeast-3 Asia Pacific (Osaka) | $4.2500 | $1.2900 | $1.2600 | $0.3150 | $42.50 |
| ap-southeast-1 Asia Pacific (Singapore) | $4.2500 | $1.2500 | $1.1500 | $0.2880 | $42.50 |
| ap-southeast-2 Asia Pacific (Sydney) | $3.5000 | $1.2900 | $1.3000 | $0.3250 | $35.00 |
| ap-southeast-3 Asia Pacific (Jakarta) | $4.2500 | $1.2900 | $1.2600 | $0.3150 | $42.50 |
| ap-southeast-4 Asia Pacific (Melbourne) | $3.5000 | $1.2900 | $1.3000 | $0.3250 | $35.00 |
| ap-southeast-5 Asia Pacific (Malaysia) | $3.8250 | $1.1250 | $1.0350 | $0.2592 | $38.25 |
| ap-southeast-6 Asia Pacific (New Zealand) | $3.6750 | $1.3545 | $1.3650 | $0.3413 | $36.75 |
| ap-southeast-7 Asia Pacific (Thailand) | $3.8250 | $1.1250 | $1.0350 | $0.2592 | $38.25 |
| ap-east-1 Asia Pacific (Hong Kong) | $4.6750 | $1.3800 | $1.2650 | $0.3168 | $46.75 |
| ap-east-2 Asia Pacific (Taipei) | $3.8250 | $1.1610 | $1.1340 | $0.2835 | $38.25 |
| ap-south-1 Asia Pacific (Mumbai) | $3.5000 | $1.0500 | $1.0000 | $0.2500 | $35.00 |
| ap-south-2 Asia Pacific (Hyderabad) | $3.5000 | $1.0500 | $1.0000 | $0.2500 | $35.00 |
| sa-east-1 South America (Sao Paulo) | $4.2500 | $1.5900 | $1.5500 | $0.3880 | $42.50 |
| mx-central-1 Mexico (Central) | $3.6750 | $1.0500 | $1.0500 | $0.2625 | $36.75 |
| me-central-1 Middle East (UAE) | $3.8500 | $1.2200 | $1.2500 | $0.3140 | $38.50 |
| me-south-1 Middle East (Bahrain) | $3.8500 | $1.2300 | $1.2540 | $0.3135 | $38.50 |
| il-central-1 Israel (Tel Aviv) | $3.8500 | $1.2200 | $1.2540 | $0.3135 | $38.50 |
| af-south-1 Africa (Cape Town) | $4.1700 | $1.3200 | $1.3600 | $0.3400 | $41.70 |
| us-gov-east-1 AWS GovCloud (US-East) | $3.5000 | $1.0000 | $1.2000 | $0.3000 | $35.00 |
| us-gov-west-1 AWS GovCloud (US-West) | $3.5000 | $1.2600 | $1.2000 | $0.3000 | $35.00 |
No matching regions found.
REST API cache sizes
Hourly rate per size, for US East (N. Virginia)| Cache size | Per hour | Per 730-hour month |
|---|---|---|
| 0.5 GB | $0.0200 | $14.60 |
| 1.55 GB | $0.0380 | $27.74 |
| 6.05 GB | $0.2000 | $146.00 |
| 13.5 GB | $0.2500 | $182.50 |
| 28.4 GB | $0.5000 | $365.00 |
| 58.2 GB | $1.0000 | $730.00 |
| 118 GB | $1.9000 | $1,387.00 |
| 237 GB | $3.8000 | $2,774.00 |
A dedicated cache is billed for every hour it is provisioned, whether or not it serves a hit. Sizes are as the price list names them; this page does not say how many requests each size absorbs.
API Gateway Portals
Monthly fees, for US East (N. Virginia)| Item | Unit | Rate |
|---|---|---|
| Portal | per portal per month | $125.00 |
| Portal product | per product per month | $12.50 |
Portals are a developer-portal feature priced per month rather than per request, so they are not in the estimator. A dash means the price list has no rate for the region; it has none for either AWS GovCloud (US) region.
Alternatives to API Gateway
| Option | Price vs API Gateway | Why look at it |
|---|---|---|
| HTTP API instead of REST API | -71%-$2.50/1M requests first request band, us-east-1 | Same request unit at a lower rate. HTTP APIs offer fewer features than REST APIs, so check you do not rely on one that is missing. They have no cache in this price list. |
| Application Load Balancer | Billed per hour and per LCU, not per request | Routes HTTP traffic to your own targets with no per-request API fee. It has none of API Gateway's API management features. |
What to know about Amazon API Gateway
A managed front door for APIs, billed per request, per message and per connection minute, with an hourly cache on REST APIs. HTTP APIs charge about 70% less per request than REST APIs.
The cheapest decision on your API Gateway bill is the API type. A REST API costs $3.50 per million requests in us-east-1. An HTTP API costs $1.00. At 10 million requests a month that is $35 against $10, for the same calls.
Both are priced per request, so the bill moves with your traffic and an idle API costs nothing. That is the case for API Gateway over a load balancer on small or spiky APIs.
HTTP APIs offer fewer features than REST APIs, so the saving is only yours if nothing you rely on is missing. Check that before you move, not after.
Request prices step down with volume. Each band’s rate covers only the requests inside it, like income tax. A REST API pays $3.50 on the first 333 million requests a month, $2.80 on the next 667 million, then $2.38 and $1.51. One billion requests costs $3,033.10. Four regions (Sydney, Melbourne, New Zealand and São Paulo) publish a different schedule, with three bands and the first running to 1 billion. The tier table on this page follows whichever region you pick.
HTTP APIs have two bands: $1.00 per million for the first 300 million, then $0.90. That second band is a 10% step, which is easy to ignore.
WebSocket APIs bill two meters at once. Messages cost $1.00 per million for the first billion, then $0.80. Every connection also pays $0.25 per million connection minutes. A month has 43,800 minutes, so a thousand clients that stay connected all month cost $10.95, whether or not they say anything. AWS meters messages in 32 KB increments, so a 33 KB message counts as two.
Think of the REST cache as renting a table at a market. It costs the same whether or not anyone buys. The smallest size, 0.5 GB, is $0.02 an hour, about $14.60 a month. A 6.05 GB cache is $146. The 237 GB cache is $3.80 an hour, about $2,774 a month. The cache is provisioned per stage, so a cache on dev, staging and prod is three caches on the bill. Price a cache against the requests it saves you, not against the size you hope to need.
Some things are not in the price list. API Gateway has no always-free allowance. Its old 12-month free tier only covered accounts opened before 15 July 2025, and newer accounts get AWS Free Tier credits instead, so the estimator doesn’t model one. Data transfer out is billed at EC2 data transfer rates. A private API adds PrivateLink charges. Your backend, whether Lambda or containers, is its own bill. Everything here is on-demand. The offer has no reserved or Savings Plans rates.
API Gateway Portals, a developer-portal feature, is billed monthly instead: $125 per portal in us-east-1 plus $12.50 per product. Neither AWS GovCloud (US) region sells it.
If nothing in your API is REST-only, move it to an HTTP API and compare the bill. If it needs a cache, price the cache first.
Good for
- Putting authentication, throttling and a stable URL in front of Lambda or other backends
- WebSocket APIs where AWS holds the connections for you
- Low-traffic APIs, where per-request billing beats paying for an idle load balancer
Watch for
- A REST API costs $3.50 per million requests in us-east-1 and an HTTP API $1.00, for the same call
- A REST cache bills every hour it exists, per stage, from $14.60 a month to about $2,774 for the largest size
- The volume discounts need hundreds of millions of requests a month, so most APIs never see them
- Data transfer out, the backend and private-API endpoint charges are billed on other lines
- WebSocket messages are metered in 32 KB increments, so a 33 KB message counts as two