Helius integration
Knot uses Helius to process and enrich transaction data before delivering webhook events. The webhook endpoint receives parsed, human-readable transaction data rather than raw Solana transaction bytes.Webhook configuration is managed server-side. Contact support to enable webhooks for your agent.
Webhook endpoint
Knot exposes an endpoint that Helius posts events to:Payload format
Helius delivers enhanced transaction data in its standard webhook format:Payload fields
The event type. See event types below.
Always
"HELIUS" for Helius-delivered webhooks.The Solana transaction signature. Use this to look up the transaction on-chain.
Unix timestamp of when the transaction was confirmed.
List of native SOL transfers in this transaction, with sender, recipient, and lamport amount.
List of SPL token transfers in this transaction, with sender, recipient, token mint address, and amount.
Event types
| Type | Description |
|---|---|
TRANSFER | Native SOL or SPL token transfer |
SWAP | Token swap via a DEX |
NFT_SALE | NFT purchase or sale |
NFT_MINT | NFT minting event |
Use cases
Balance updates
Refresh your internal balance cache when transactions are confirmed on-chain.
Notifications
Trigger alerts or agent actions when the wallet receives incoming funds.
Incoming transfers
Track deposits and incoming payments from external sources.
Transaction confirmations
Confirm that outgoing transactions have settled and been finalized.
Setup overview
Provide your wallet address
Supply your agent’s wallet address so Knot can configure the Helius subscription for your account.
Receive events
Knot begins receiving Helius events for your wallet. Balance state and audit logs are updated in real time.
Native SOL amounts in webhook payloads are denominated in lamports. Divide by 1,000,000,000 to convert to SOL.