Practical guide
API Gateway HTTP API pricing: requests vs billable units
calculate API Gateway HTTP API billable request units. Includes a worked example, calculator scope, and practical questions.
Updated · Sources checked
One API call is not always one billing unit
The HTTP API calculator uses billable 512 KB request units in millions. Request count alone can understate usage when payloads cross the applicable billing increment. Start with the HTTP API pricing model; REST APIs and WebSocket APIs use different structures and do not belong in the same input.
Classify requests by payload size before multiplying. Rounding applies at the request level, so dividing the total monthly payload by a billing increment can produce the wrong answer.
Worked example: mixed payload sizes
Suppose a month has eight million HTTP API calls with payloads within one billable increment, plus one million calls with 700 KB payloads. Using the documented 512 KB increment, the first group contributes eight million units and the second contributes two million units.
Total modeled volume is ten million billable request units even though the application made nine million calls. Enter 10 in a field labelled millions of billable request units. Entering 10,000,000 there would multiply the intended volume by a million.
This example isolates request billing. It does not claim that a 700 KB request implies a 700 KB response, nor does it estimate outbound transfer. If retries reach the API, include their applicable billable activity in the measured request totals rather than counting only successful business operations.
Apply the right tier schedule
The calculator uses the supported US East HTTP API tiers and does not apply an introductory free tier. Keep any eligibility-based benefit separate until verified for the account. A lower rate at a later tier applies to the corresponding slice of usage, not automatically to the entire month’s requests.
Its subtotal omits Lambda or other backend execution, transfer, authentication dependencies, logging, and other services. A complete serverless endpoint budget needs those additional lines even when the request charge is modest.
Frequently asked questions
Can I enter REST API calls here? No. This tool is scoped to HTTP APIs.
Is monthly payload divided by 512 KB sufficient? No. Derive rounded units per request or per size cohort, then sum them. Request-level rounding is why a mixed-payload estimate needs more than one average byte total.
Calculate your scenario
Use the api gateway cost calculator. Keep the displayed region, pricing date, billing units, and exclusions alongside your result. The arithmetic examples above illustrate usage or explicitly hypothetical rates; they are not AWS quotes.
Source
Billing structure checked against official AWS documentation on September 6, 2026.