Credits and Rate Limits

Up to 100,000 addresses using the API.
Yes, editing a webhook via the API or dashboard costs 100 credits per request. This applies to any modification including URL changes, adding/removing addresses, or updating transaction types.
Each webhook event costs 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 returns an error.
All webhook management operations (create, edit, delete) cost 100 credits per request when performed via the API. This covers the processing required to update your webhook configurations.

Supported Networks

Yes! Set "network":"devnet" when creating your webhook to monitor Devnet transactions and events.
No—the URL must be publicly reachable over HTTPS. Helius cannot access local development servers via localhost URLs.

Using Webhooks

Set an authorization header when creating or updating the webhook. Helius echoes this value in the Authorization header when sending data to your webhook endpoint, allowing you to verify the request’s authenticity.
Raw webhooks return regular Solana transaction data directly from the blockchain. When a transaction occurs for the monitored addresses, the raw transaction data is sent to your webhook URL.Enhanced webhooks provide Helius’ interpreted transaction types. We parse over 100 types of Solana transactions (NFT listings, DeFi swaps, transfers, etc.) and abstract them into our own schema.Use raw webhooks if you want all transaction data without abstractions, or enhanced webhooks if you want built-in transaction type detection and parsing.
Webhooks send notifications immediately after a matching transaction is confirmed on the blockchain.

Retries

Helius retries unacknowledged webhook events up to 3 times with a 1-minute interval between attempts. We also offer customizable retry policies for enterprise plans.
It depends on the webhook type. Enhanced webhooks do not send failed transactions, but raw webhooks do include both successful and failed transactions.

Troubleshooting Webhooks

Data dropping typically occurs when your endpoint encounters an error, causing webhook retries that eventually fail and lead to data loss. Check your webhook logs in the dashboard, ensure sufficient client-side logging is in place, and contact support if the problem persists.
Ensure the selected transaction type matches the transactions you’re monitoring. Start with the “ANY” transaction type to identify if it’s a general issue or a type mismatch. Use webhook.site to test if the problem lies with your endpoint configuration.
The TOKEN_MINT webhook only triggers for specific programs like Candy Machine V1, and Solana Program Library. It doesn’t cover all token minting events across the entire blockchain. For broader monitoring, consider using a more general account or program subscription via webhooks with “ANY” transaction type filtering.

Need More Help?