Spectrum Nodes
Push, don't poll

On-chain events, the moment they happen

Spectrum Webhooks watches the chain and pushes a signed HTTPS request to your endpoint whenever an address you care about moves value. No polling, no node to run, no missed blocks, just a clean JSON payload for every relevant event.

POST /webhooks/spectrum200 OK
{
"type": "ADDRESS_ACTIVITY",
"category": "token",
"value": "1000",
"asset": { "symbol": "USDC" },
"blockNumber": 19000000,
"removed": false
}
HMAC ✓X-Spectrum-Signature: t=…,v1=…

1 block

Typical delivery latency

Pushed the moment an event is confirmed

At-least-once

Durable, retried delivery

Retries until your server returns 2xx

Replace your indexer and your polling loops

Building on-chain usually means running an archive node with a custom indexer, or hammering a public RPC with polling that is slow, rate-limited, and still misses reorgs. Webhooks replaces both.

Stop polling

Get a push the instant an event is confirmed, typically within one block. No loops, no rate limits, no missed blocks.

Never miss an event

Durable, at-least-once delivery with automatic retries survives your endpoint being down, then a dead-letter queue you can replay.

Reorg-aware

When the chain reorganizes we flag which events to roll back, so you are never quietly left holding bad data.

Signed and verifiable

Every POST is HMAC-signed with a per-webhook secret and timestamp, so you can prove origin and reject replays.

From on-chain event to your endpoint

We ingest and decode every block, match it against your filters, sign it, and deliver, retrying until your server acknowledges. Everything is durably queued first, so an outage on either side never loses an event.

On-chain event

Block confirmed

HMAC

Spectrum

Decode & sign

Your endpoint

Verify & 2xx

  1. 1

    Ingest and decode

    We subscribe to the chain and decode every block: native, internal, and token transfers.

  2. 2

    Match your filters

    Each event is matched against your webhook's addresses, token, and category filters.

  3. 3

    Sign and batch

    Matching events are batched by block, signed with your secret, and ordered deterministically.

  4. 4

    Deliver and retry

    We POST to your endpoint and retry with backoff until 2xx; persistent failures go to a dead-letter queue.

Every kind of transfer, decoded

Watch an address as sender or receiver, narrowed by token contract and category. Every event arrives with human-readable amounts and token metadata, so you never need a second RPC call to make sense of it.

external

Native coin transfers (e.g. ETH) sent as a top-level transaction.

internal

Native value moved inside a contract call, recovered from execution traces and invisible in logs.

token

ERC-20 fungible token transfers, with symbol and decimals resolved.

erc721

NFT transfers, including the tokenId.

erc1155

Single and batch multi-token transfers.

Built for every on-chain trigger

One durable, signed event stream behind deposit detection, treasury monitoring, payments, alerting, and analytics.

Deposit detection

Credit users the moment funds land on your hot or deposit addresses, including internal transfers that log-only services miss.

Treasury monitoring

An audit trail of every inflow and outflow for your org wallets, with amounts already denominated in token units.

NFT activity feeds

Track mints, sales, and transfers for a collection or a set of holders in real time.

Payments and invoicing

Trigger fulfillment the instant a specific token payment hits your receiving address.

Security and alerting

Fire a Slack or PagerDuty alert when a monitored treasury or multisig moves unexpectedly.

Analytics pipelines

Stream decoded, normalized on-chain events straight into your data warehouse without running an indexer.

Start delivering

Ship real-time on-chain events today

Create a webhook, point it at your endpoint, and start receiving signed, decoded events. No nodes, no polling, no missed blocks.

Free tier included · No credit card required