Technical Details:
The calculation expands the selected traffic scale, adds retry or replay overhead and rounds payloads up to the billing increment for the chosen family. Any enabled allowance is subtracted after chunking, never from raw business transactions.
Formula Core:
The common traffic path is:
o is retry overhead percent. The chunk factor k is the ceiling of request KB divided by 512 for HTTP APIs, message KB divided by 32 for WebSocket APIs, or streamed response KB divided by 10,240 for REST response streaming. Other REST paths use one unit per call.
Tiered request or message cost sums the units in each tier:
Ti and ri are units and USD-per-million rate in tier i; m is the selected regional multiplier. The built-in planning card uses these rate tiers:
Built-in API Gateway request and message planning rates
| Family | Tier | Rate per million |
| HTTP API | First 300 million | $1.00 |
| HTTP API | Over 300 million | $0.90 |
| REST API | First 333 million | $3.50 |
| REST API | Next 667 million | $2.80 |
| REST API | Next 19 billion | $2.38 |
| REST API | Over 20 billion | $1.51 |
| WebSocket API | First 1 billion messages | $1.00 |
| WebSocket API | Over 1 billion messages | $0.80 |
Built-in API Gateway secondary planning rates and multipliers
| Item | Built-in value |
| WebSocket connection minutes | $0.25 per million minutes |
| Public response transfer | $0.09 per GB |
| REST cache example | $0.038 per hour for 730 hours |
| Private endpoint | $0.01 per AZ-hour plus $0.01 per GB |
| Developer portal | $125 per portal plus $12.50 per product monthly |
| Rate profiles | 1.00 standard; 1.21 regional premium; 1.34 high premium |
Public HTTP and REST response transfer is response bytes divided by 1,048,576 KB per GB, less the entered included GB, multiplied by the transfer rate. Private REST data uses request plus response bytes and adds endpoint hours for each Availability Zone. WebSocket connection minutes equal average connections multiplied by connected hours per day, 60 minutes and a 30-day month.
The built-in allowance removes up to one million request or message units and, for WebSocket APIs, 750,000 connection minutes. It is applied only when enabled and does not establish account eligibility. Calculations retain full precision; displayed USD values are formatted for reading.