API Gateway REST vs HTTP API cost: which is cheaper

Quick answer

AWS API Gateway HTTP APIs cost roughly a third to a fifth of what REST APIs cost per million requests, so for high-volume, simple proxying to Lambda or HTTP backends, HTTP APIs are the clear cost winner. REST APIs cost more but add features HTTP APIs lack: request/response transformation, API keys and usage plans, request validation, private endpoints via VPC link with more control, WAF integration, and edge-optimized endpoints. Choose HTTP APIs by default for cost, and only pay for REST when you genuinely need one of its exclusive features.

AWS API Gateway comes in two flavors, REST APIs and HTTP APIs, that do similar jobs at very different prices. If you are proxying requests to Lambda or an HTTP backend at volume, the choice materially affects your bill, because HTTP APIs are priced well below REST APIs per request.

The price gap

Type	Relative per-request price	Best for
HTTP API	Roughly a third to a fifth of REST	High-volume simple proxying
REST API	Higher, the premium tier	Feature-rich or legacy APIs

Both charge per million requests received, with tiered pricing that drops the unit rate at very high volume, plus any data transfer out. But HTTP APIs are dramatically cheaper per million requests, so at scale the gap compounds into real money. For a service handling hundreds of millions of requests a month, moving from REST to HTTP API can cut the API Gateway line item by well over half.

What REST APIs give you for the premium

REST APIs cost more because they do more. Features that HTTP APIs do not offer (or offer in reduced form) include request and response transformation and mapping templates, API keys with usage plans and throttling per key, request validation, AWS WAF integration, edge-optimized endpoints via CloudFront, and richer private integration controls. If your API depends on mapping templates to reshape payloads, or sells access through usage plans and API keys, REST may be doing work you would otherwise have to rebuild.

What HTTP APIs cover well

HTTP APIs handle the common case efficiently: proxy to Lambda or any HTTP endpoint, JWT and OIDC authorization, CORS, custom domains, and automatic deployments. For a modern serverless backend where the Lambda function does the request handling and you just need a fast, cheap front door, HTTP APIs cover it. Most greenfield serverless APIs do not need REST-only features, which is why HTTP APIs are the sensible default.

How to choose

Default to HTTP APIs for cost, and reach for REST only when you genuinely need a REST-exclusive feature you cannot easily replicate. If you have an existing REST API at high volume, audit whether you actually use its premium features; many teams pay the REST premium for features they never touch, and could migrate to HTTP APIs for a large saving. For comparison with fully managed data-driven APIs, seeAppSync vs API Gateway, and remember that whichever you pick, the data transfer out and the downstream Lambda or compute cost sit alongside the gateway charge. Placing the API in acost-effective region trims the surrounding compute cost too.

FAQ

Is API Gateway HTTP API cheaper than REST API?

Yes, substantially. HTTP APIs cost roughly a third to a fifth of what REST APIs cost per million requests. For high-volume APIs the gap compounds into real money, so moving a busy service from REST to HTTP API can cut the API Gateway line item by well over half. Both also charge for data transfer out, which is the same either way.

What features do REST APIs have that HTTP APIs lack?

REST APIs add request and response transformation with mapping templates, API keys with usage plans and per-key throttling, request validation, AWS WAF integration, edge-optimized endpoints via CloudFront, and richer private integration controls. HTTP APIs omit or reduce these to hit a lower price. If your API depends on mapping templates or sells access through usage plans and keys, REST may be doing real work for the premium.

When should I use a REST API despite the higher cost?

When you genuinely need a REST-exclusive feature you cannot easily replicate: mapping templates to reshape payloads, API keys and usage plans for monetized or throttled access, request validation, WAF integration, or edge-optimized endpoints. If you do not use any of those, the REST premium is wasted, and HTTP APIs deliver the same core proxying for a fraction of the price.

Can I migrate an existing REST API to an HTTP API?

Often, yes, if you are not relying on REST-only features. The migration is a rebuild of the API definition rather than a flip of a switch, so audit which premium features you actually use first. Many teams find they pay the REST premium for mapping templates or usage plans they never touch, in which case migrating to an HTTP API captures a large recurring saving with little functional loss.

What else costs money alongside API Gateway?

Data transfer out of the gateway, and the downstream compute the API invokes: Lambda functions, containers, or backend servers, which are billed separately. For a serverless API, the Lambda execution cost often exceeds the gateway request cost. So when you estimate API cost, add the gateway request charge, the data transfer out, and the backend compute together rather than looking at the gateway line alone.

Does C3X price API Gateway in Terraform?

C3X prices infrastructure from your Terraform before deploy, so an API Gateway definition (REST or HTTP) is costed against a live catalog in the pull request. That helps you see the cost difference between choosing a REST versus an HTTP API at your expected request volume before you commit, alongside the Lambda or backend resources the API fronts.

What to do next

Compare REST and HTTP API cost before you build. C3X prices your Terraform against a live resource catalog. Start with the quickstart.