Crypto Whale Webhook APIs: Real-Time Whale Transaction Alerts Compared

Polling an API every few seconds is the simplest way to watch whale moves, and it is also the most wasteful: most polls return nothing new, and every poll counts against your rate limit. A webhook flips the direction. The provider sends a POST to your server when something happens, and your bot or desk tool reacts. For trading desks, alert bots and research pipelines, the questions are what triggers a delivery, how fast it arrives, and what happens when your endpoint is down.

What Deep Blue Alpha pushes today

Every paid plan from Pro upward includes alerts on coins, wallets and event types you choose. Each alert can be delivered to Telegram, browser push, email, Discord, Slack or a generic webhook. The generic webhook sends this JSON body to an HTTPS URL you provide:

{
  "source": "deepbluealpha.io",
  "alert_type": "...",
  "timestamp": "2026-10-16T11:32:35+00:00",
  "token_symbol": "LINK",
  "wallet_address": "0x...",
  "usd_value": 250000,
  "direction": "...",
  "message": "...",
  "url": "https://deepbluealpha.io/alerts"
}

What to know: these are alerts you configured, not a feed of every whale move; each delivery is a single attempt with a 10-second timeout; loopback and private-network URLs are refused. These alerts are part of personal plans. See /alerts.

What the Business firehose webhook adds (launching soon)

The Business plan, announced at /business with checkout opening soon, adds a webhook built for systems rather than people. As described on the Business page, it is planned to include:

• One POST to your URL for each tracked whale move (20,000+ wallets), not only the alerts you set up.
• Filters by coin, move type (exchange deposit, exchange withdrawal, DEX swap) and minimum USD size.
• Signed payloads you can verify, retries with backoff and a delivery log.
• Automatic pause with an email to you if your endpoint keeps failing.

Until it ships, the reliable way to receive every tracked move is to poll /api/v1/transactions with before_id pagination on the Whale plan (25,000 calls/day, personal use).

Push options from other providers

How fast is “real time” on Ethereum?

Ethereum produces a block about every 12 seconds. Deep Blue Alpha reads new blocks as they arrive and writes a row for each transfer or swap that touches a tracked wallet; at Oct 16, 2026 11:34 UTC the public stats endpoint showed the newest recorded move at 11:32 UTC. Moves can arrive late or be revised during provider outages or chain reorganizations, which is why a pull-API backstop is worth keeping.

Setting up a whale webhook consumer

1. Pick the trigger you need. Every move by a tracked wallet set (firehose), moves above a USD size, or only the coins and wallets you choose. Each provider supports a different subset.
2. Check the size floor. Whale Alert WebSocket alerts start at $100,000 per transfer. Deep Blue Alpha alerts let you set your own coins, wallets and alert types.
3. Check delivery guarantees. Ask whether payloads are signed, whether failed deliveries are retried and whether there is a delivery log. Today's Deep Blue Alpha alert webhooks are single attempts with a 10-second timeout; signing, retries and a delivery log are part of the planned Business firehose.
4. Make your endpoint idempotent. Use the transaction hash plus wallet and direction as a key so a repeated delivery does not double-count a move.
5. Reconcile with a pull API. Poll /api/v1/transactions with before_id pagination as a backstop so a missed push is caught on the next poll.

Plans