AWS API Gateway Cost Calculator

Start by separating API type and traffic path

The quickest way to break an API Gateway estimate is to treat all traffic as one blended stream. Before trusting the total, split traffic by API type and by delivery path: public internet responses, private integration traffic, cached responses, and any large-payload endpoints that behave differently from the median route.

• Measure monthly requests from CloudWatch, access logs, or billing exports rather than from one recent day.
• Break out endpoints with unusually large response bodies instead of using one global average response size.
• Write down whether transfer is really internet egress, private connectivity, or mostly absorbed by CDN caching.

Where API Gateway estimates usually drift

API Gateway pages often look request-driven at first, but the bill drifts when one of the hidden multipliers grows faster than request count.

• Retry storms: timeouts, client retries, and webhook redelivery can multiply request volume quickly.
• Log-heavy endpoints: access logs and downstream observability are adjacent costs that this page does not include.
• Large responses: file-like or report-like endpoints can turn transfer into the dominant line item.
• Cache miss behavior: a cache that is cold during launches or incidents can make peak months look nothing like baseline months.

Reconcile the estimate with a real bill

If the calculator and the bill disagree, do not start by editing prices. First confirm the traffic shape and the boundary you are paying for.

1. Pull one representative billing period and compare billed requests with your measured request count.
2. Check whether the routes with the highest payload size are also the routes with the highest call count.
3. Confirm whether CDN, WAF, custom domains, or private integrations are adding adjacent charges outside this page.
4. Re-run the calculator with separate baseline and launch or incident scenarios instead of one monthly average.

What to do after the first estimate

If request fees dominate, focus on caching, batching, and noisy clients. If transfer dominates, reduce payload size, compress aggressively, or hand off large responses to a CDN workflow. If both move together, this page is a planning checkpoint and the next review should include logs, WAF, and backend dependencies.

Next steps