Request fees vs bandwidth
Small responses stay request-bound, big JSON or media payloads tip the bill toward egress.
Home / Dev & AI / API & Backend Cost / Webhook Cost Calculator
API & Backend Cost
Webhook Cost Calculator
Estimate what webhooks cost at scale. Enter monthly events, the price per million and average payload size, and see delivery fees, bandwidth and growth.
Estimated monthly cost
$0
Request cost—
Bandwidth cost—
Cost per 1,000 requests—
Data transferred / month—
Requests per month—
Annual estimate—
Cost as traffic grows
What this endpoint costs if monthly volume doubles, 5x or 10x.
What the Webhook Cost Calculator does
Webhooks push events to a URL as things happen, and at scale each delivery has a cost. Whether you send webhooks to customers or process incoming ones, you pay for the compute that fires or handles each event plus the bandwidth of the payload. High volume event streams can add up quickly.
This webhook cost calculator treats each event like a request: it applies a per million delivery price and adds bandwidth from the payload size, giving you a monthly figure and a projection as event volume grows. Retries on failed deliveries effectively raise your volume, so pad your estimate if your endpoints are unreliable.
Heads up on pricing. The rates built into this tool are public list estimates for July 2026 and can change without notice. Providers also offer batch discounts, prompt caching and volume tiers that lower real costs, so treat the output as a planning estimate, not a quote.
The formula
delivery cost = events ÷ 1,000,000 × price per million
bandwidth = events × avg KB ÷ 1,000,000 × egress price
total = delivery cost + bandwidth
bandwidth = events × avg KB ÷ 1,000,000 × egress price
total = delivery cost + bandwidth
Worked example
Sending 5,000,000 webhook events a month at $0.50 per million with 40 KB payloads at $0.09 per GB, delivery is 5 × $0.50 = $2.50 and bandwidth is 200 GB × $0.09 = $18, for about $20.50 a month.
Ways to lower your API and backend costs
- Serve responses through a CDN. Cached, edge-delivered responses cut egress cost and take load off your origin.
- Compress payloads. gzip or brotli plus trimming unused JSON fields reduces bandwidth on every single request.
- Cache common responses. Avoid recomputing identical results for repeated reads, which lowers both compute and request fees.
- Reduce chatty designs. Combine several small calls into one batch endpoint or a single GraphQL query to cut request volume.
- Right size and autoscale. Match capacity to real peak traffic instead of paying for servers that sit idle most of the day.
Frequently asked questions
How much do webhooks cost?
Delivery itself is cheap per event, often well under a dollar per million, with bandwidth usually the larger part. Volume and retries drive the total. Enter your numbers above.
Do retries increase cost?
Yes. Each retry is another delivery and another payload sent, so flaky endpoints that trigger many retries can multiply your effective event volume.
How do I reduce webhook costs?
Batch events where possible, keep payloads lean, use exponential backoff to limit retries, and let consumers pull large data rather than pushing it all.
Should I use webhooks or polling?
Webhooks are cheaper and timelier than frequent polling for event driven updates, since polling wastes calls when nothing has changed.
Are these estimates exact?
They are 2026 planning estimates. Confirm your compute and egress rates for a precise figure.