Skip to main content

What are Solana webhooks?

Solana webhooks are real-time HTTP notifications sent to your application when on-chain events occur. Instead of continuously polling the blockchain, Helius pushes parsed transaction data directly to your endpoint whenever a wallet transfers funds, an NFT sells, or any monitored transaction type fires. Use webhooks to power trading bots, analytics dashboards, compliance pipelines, and event-driven automation. We offer a user-friendly interface, programmatic API, and SDK access for easily creating and managing webhooks. For frequently asked questions, see the Webhooks FAQ.
Helius may retry webhook deliveries if your server does not respond successfully, and you might receive duplicate events. For details on retries and handling duplicates, see the Webhooks FAQ.

Pricing

Webhook events are charged at 1 credit when Helius processes and sends the event to your endpoint. You are charged regardless of whether your endpoint successfully processes the webhook or not. Editing, adding, or deleting a webhook via the API will cost 100 credits/request.

Types of Webhooks

We currently offer several types of webhooks tailored to different needs:

Enhanced Transaction Webhooks

Provide human-readable, parsed data for specific transaction types (e.g., NFT sales) related to the addresses you monitor. This is ideal if you want filtered, actionable insights.

Raw Transaction Webhooks

This option delivers raw transaction data for all transactions involving the addresses you monitor. It does not allow filtering by transaction type.
Raw Transaction Webhooks offer lower latency since they do not involve parsing event types.

Discord Webhooks

Stream updates for specific transaction types directly to a designated Discord channel as formatted messages. To use this option, you must submit your Discord Webhook URL.

Event Payload Example

Get Started

Webhooks Quickstart

Create your first webhook via the Dashboard, REST API, or official TypeScript / Rust SDK.

Automatic Disabling of Failing Webhooks

Helius monitors webhook endpoint health and automatically disables webhooks that consistently fail to receive deliveries. This prevents wasted delivery attempts against unreachable or broken endpoints.

How It Works

  • Paid plans (Dev and above): Webhooks with a ≥ 95% failure rate over 7 days are automatically disabled.
  • Free plan: Webhooks are evaluated over a 24-hour window with the same failure threshold.
The system checks webhook health every 4 hours. When a webhook is disabled, deliveries stop within seconds.

Email Notifications

Users on the Dev plan and above receive an email notification when a webhook is automatically disabled.

Re-enabling a Disabled Webhook

1

Fix your endpoint

Resolve the issue causing delivery failures (e.g., server downtime, incorrect URL, endpoint errors).
2

Log in to the Helius Dashboard

Go to the Helius Dashboard.
3

Re-enable the webhook

Find the disabled webhook and toggle it back on.
You can also re-enable webhooks programmatically via the Toggle Webhook API endpoint.
After re-enabling, the webhook enters a 24-hour grace period during which it will not be automatically disabled again. This gives you time to verify that your endpoint is healthy.

Example Uses

Bots

  • When an NFT is listed on marketplace X, trigger an “NFT buy” action.
  • When a margin position is unhealthy, trigger a “liquidation” action.

Monitoring & Alerts

  • When a program emits a certain log, it triggers PagerDuty integration.
  • When a token account balance changes by more than X%, use Dialect to communicate a warning action.

Event-driven Indexing

  • When any transaction occurs for a given program, send it directly to your database or backend.

Notifications & Activity Tracking

  • When transferring from wallet X to wallet Y — send a Slack notification or email.

Analytics & Logs

  • When event X happens, send it to an ETL pipeline or persist it directly on Helius to view trends over time.

Workflow Automation

  • When event X happens, trigger any set of actions.