What are GetBlock webhooks?

They push on-chain events to your HTTPS endpoint. Set a trigger and filters once; GetBlock checks every new block and sends each match as a signed JSON POST request.

Which networks and events are supported?

Ethereum mainnet today. You can watch wallet activity, contract logs and transaction confirmations. BNB Smart Chain, Polygon and Base come next.

How are webhooks billed?

Each delivery attempt costs 25 CU from the same balance as RPC requests. Both phases, reorg corrections, retries and failed attempts are billed, so an event that fails all 8 attempts costs up to 200 CU. Test deliveries are free.

What happens during a chain reorganization?

If the block with your event leaves the chain, you get a correction for that event so you can undo it. Corrections come with the unconfirmed phase: subscribe to it to hear about late reorgs.

What if my endpoint is down?

A failed delivery is retried up to 8 times over about 52 minutes. If deliveries keep failing for 30 minutes with at least 20 failed attempts, the webhook is paused until you resume it.

Can I get the events I missed?

Not in v1: there is no replay. An event that fails all 8 attempts is recorded as failed in the delivery history, and events that happen while a webhook is paused are not matched.

What are the limits on my plan?

Your plan sets the number of active webhooks, the addresses per webhook and per account, and the events per second — from 1 webhook and 10 addresses on Free to 100 webhooks and 1,000,000 addresses per account on Premium.

GetBlock

Webhooks

On-chain events, delivered to your endpoint

Set a trigger and filters once. GetBlock watches every new block and sends each matching event to your HTTPS endpoint — signed, retried and corrected on reorgs.

Create a webhook

25 CU
per delivery attempt
8 attempts
retried over about 52 minutes
HMAC-SHA256
signature on every delivery
250,000
addresses per webhook on Scale and up

WHY WEBHOOKS

Stop polling. Start reacting.

Polling burns requests on empty blocks. Webhooks call you only when something happens.

No polling loop

GetBlock watches every new block and pushes only matching events.

Precise filters

Match by address, contract and topic. Watch up to 250,000 addresses per webhook on Scale and up.

Reorg-aware by design

Subscribe to first inclusion, confirmation or both. If a block is dropped, you get a correction.

Signed and retried

Every request is signed with HMAC-SHA256. A failed delivery gets up to 8 attempts.

USE CASES

Built for products that react to the chain

One endpoint replaces a poller and a scanner.

Wallet notifications

Alert users when ETH or tokens move in or out.

Deposit confirmation

Credit deposits once they reach the confirmation depth you choose.

DeFi and contract alerts

Follow swaps, liquidations or governance events by contract and topic.

NFT activity

Track mints and transfers of the collections you follow.

Compliance monitoring

Watch lists of up to 100,000 addresses and route every hit.

Analytics pipelines

Stream matched events into your queue or warehouse.

HOW IT WORKS

Live in three steps

Use the dashboard or the API.

Pick a trigger and filters
Wallet activity, contract logs or transaction confirmations.
Add your HTTPS endpoint
Store the secret and verify every signature.
Receive events
Acknowledge within 15 seconds; undo reorged events.

Network coverage

Live

Ethereum

BNB Smart Chain
Polygon
Base

Webhooks v1 runs on Ethereum mainnet. BNB Smart Chain, Polygon and Base are on the roadmap and cannot be selected yet.

COMPARE

Webhooks vs. other approaches

Each fits a different job.

Capability	GetBlock Webhooks	Polling RPC	WebSocket stream	Self-hosted indexer
Setup	Minutes in the dashboard	Poller plus cursor store	Client with reconnects	Nodes, indexer, storage
Infrastructure you run	One HTTPS endpoint	Workers, state	Always-on socket client	Nodes, databases, monitoring
When your service is down	8 attempts over ~52 minutes	Catch up yourself	Missed while disconnected	Replay yourself
Cost model	25 CU per attempt	CU per poll, empty too	CU per delivered event	Servers and engineering time

A comparison of approaches, not of specific providers. Your numbers depend on traffic and architecture.

PLAYGROUND

Create a webhook and watch events arrive

A simulation in your browser with mock data. Nothing is sent to GetBlock.

Create a webhook
Watch signed deliveries arrive
Break your endpoint and see the retries

PRICING

Pay per delivery attempt

Your CU plan covers webhooks and sets their limits.

25 CUper delivery attempt

From the same CU balance as RPC requests.

Every attempt is billed, retries included. Test deliveries are free. How billing works

Create a webhook

Estimate your CU

Matched events per month

Phases per event

Unconfirmed is sent when the transaction lands in a block; confirmed, when that block reaches your confirmation depth.

2,500,000 CU per month

Assumes every attempt succeeds. Retries and reorg corrections add attempts.

The Free plan includes 50,000 CU per day — about 2,000 delivery attempts.

See CU plans

Webhook limits by plan
Plan	Active webhooks	Addresses per webhook	Addresses per account	Events per second	Burst
Free	1	10	10	1	12
Starter	10	100,000	100,000	5	60
Growth	25	100,000	250,000	10	120
Advanced	25	100,000	250,000	10	120
Scale	50	250,000	1,000,000	20	240
Pro	75	250,000	1,000,000	30	360
Premium	100	250,000	1,000,000	50	600
Enterprise	Premium's limits, or as agreed

Paused webhooks count toward active webhooks and addresses.
Events per second is one budget for all your webhooks. Events above it are dropped, not delayed, and are not billed.

All limits and billing rules

GOOD TO KNOW

Frequently asked questions

They push on-chain events to your HTTPS endpoint. Set a trigger and filters once; GetBlock checks every new block and sends each match as a signed JSON POST request.
Ethereum mainnet today. You can watch wallet activity, contract logs and transaction confirmations. BNB Smart Chain, Polygon and Base come next.
Each delivery attempt costs 25 CU from the same balance as RPC requests. Both phases, reorg corrections, retries and failed attempts are billed, so an event that fails all 8 attempts costs up to 200 CU. Test deliveries are free.
If the block with your event leaves the chain, you get a correction for that event so you can undo it. Corrections come with the unconfirmed phase: subscribe to it to hear about late reorgs.
A failed delivery is retried up to 8 times over about 52 minutes. If deliveries keep failing for 30 minutes with at least 20 failed attempts, the webhook is paused until you resume it.
Not in v1: there is no replay. An event that fails all 8 attempts is recorded as failed in the delivery history, and events that happen while a webhook is paused are not matched.
Your plan sets the number of active webhooks, the addresses per webhook and per account, and the events per second — from 1 webhook and 10 addresses on Free to 100 webhooks and 1,000,000 addresses per account on Premium.

Need higher limits or a custom setup?

Ship your first webhook today

Start on the Free plan: 1 webhook, 10 addresses and 50,000 CU every day.

Start for free Read the docs