API Gateway Request Volume Estimator

Model monthly API Gateway request volume from baseline RPS, peak windows, and a retry multiplier so you can feed realistic numbers into cost estimates.

Inputs

Baseline RPS (avg)
Average requests per second for normal traffic.
Baseline hours per day
Use 24 for always-on traffic.
Days per month
Request multiplier (%)
Buffer for retries, timeouts, and bots.
Peak RPS (avg)
Higher traffic during launches or spikes.
Peak hours (per month)
Total hours of higher traffic each month.
Scenario presets
Use the total requests in the AWS API Gateway cost calculator.

Results

Baseline requests
645,840,000
Peak requests
64,800,000
Total requests
817,236,000
Average RPS
311.14
Applied multiplier
115%

How to get your inputs

  • Baseline RPS: use CloudWatch or access logs for a representative week.
  • Peak windows: document launches, incidents, or scheduled batch runs.
  • Multiplier: add retries, timeouts, bots, and automated traffic.

Next steps

AWS API Gateway cost calculator Guide: estimate API requests
Advertisement

Example scenario

  • 180 RPS baseline with a 10-hour peak window and 110% retry buffer.
  • Mobile app traffic: 900 RPS baseline, 3,200 RPS peaks, and 120% multiplier.

Included

  • Baseline requests from RPS, hours/day, and days/month.
  • Peak window requests for launches, incidents, or campaigns.
  • Retry multiplier to account for timeouts and bot traffic.

Not included

  • Per-request pricing (use the API Gateway cost calculator).
  • Transfer, caching, and downstream service costs.

How we calculate

  • Baseline requests = baseline RPS x baseline hours x 3600.
  • Peak requests = peak RPS x peak hours x 3600.
  • Total requests = (baseline + peak) x retry multiplier.

FAQ

Should I include retries?
Yes. Any retries that hit the gateway are billable and should be included in request volume.
What counts as a peak window?
Launches, batch processing, incident spikes, or seasonal traffic surges.
Why not just use average RPS?
Average hides spikes. Modeling a peak window improves accuracy and avoids under-budgeting.

Related tools

AWS API Gateway cost calculator Guide: estimate API requests Guide: API Gateway pricing

Related guides

API Gateway vs ALB vs CloudFront cost: what to compare (requests, transfer, add-ons)
A practical cost comparison of API Gateway, Application Load Balancer (ALB), and CloudFront. Compare request pricing, data transfer, caching impact, WAF, logs, and the hidden line items that change the answer.
CloudFront pricing: estimate bandwidth and request costs (without hardcoding prices)
A practical way to estimate CloudFront-style CDN costs using your own bandwidth ($/GB) and request-fee ($ per 10k/1M) assumptions, plus common pitfalls like tiered pricing and origin egress.
CDN request pricing: estimate $ per 10k / 1M requests (and when it dominates)
Some CDNs charge request fees in addition to bandwidth. Learn what counts as a billable request, how to estimate requests/month from RPS or analytics, and how to model per-10k vs per-1M pricing without unit mistakes.
CloudFront cache hit rate: how it changes origin egress cost
Cache hit rate strongly influences origin requests and origin egress (cache fill). Learn a simple model, what breaks hit rate, and the practical levers to improve it safely.
Lambda vs Fargate cost: a practical comparison (unit economics)
Compare Lambda vs Fargate cost with unit economics: cost per 1M requests (Lambda) versus average running tasks (Fargate), plus the non-compute line items that often dominate (logs, load balancers, transfer).
API Gateway cost optimization: reduce requests, bytes, and log spend
A practical playbook to reduce API Gateway spend: identify the dominant driver (requests, transfer, or logs), then apply high-leverage fixes with a validation checklist.
Advertisement

Disclaimer

Educational use only. Not legal, financial, or professional advice. Results are estimates based on the inputs and assumptions shown on this page. Verify pricing and limits with your providers and documentation.

Last updated: 2026-01-30