Use case · Developers
On-chain webhooks, without the infrastructure.
Register a watch over the API, point it at your endpoint, and receive clean, signed events when a wallet moves. No node, no indexer, no reorg handling to maintain.
Built to be trusted in production
Signed payloads
Every webhook is signed so you can verify it truly came from SCMon.
Automatic retries
Transient failures are retried with backoff so you don't lose events.
IP allowlisting
Lock each API key to your server IPs — a leaked key is useless elsewhere.
Stable egress
Calls arrive from a known address you can allowlist on your side.
Manage watches over the API
Create, update and delete watches programmatically — add a watch when a user generates a deposit address, remove it when they churn. Your API key only works from the IPs you whitelist.
Example payload
POST https://your-app.example/hooks/scmon
X-Scmon-Signature: t=...,v1=...
{
"event": "transfer",
"chain": "tron",
"watch_id": "wch_...",
"token": "USDT",
"direction": "in",
"from": "T...",
"to": "T...",
"amount": "2500.00",
"tx_hash": "...",
"block": 65000000,
"ts": "2026-06-16T08:30:00Z"
}Illustrative shape — the published API reference is the source of truth at launch.
Ship on-chain events this afternoon
Skip the node. Create an account, grab a key, and start receiving webhooks.
Create your account →