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
string
The event type. See event types below.
string
Always
"HELIUS" for Helius-delivered webhooks.string
The Solana transaction signature. Use this to look up the transaction on-chain.
number
Unix timestamp of when the transaction was confirmed.
array
List of native SOL transfers in this transaction, with sender, recipient, and lamport amount.
array
List of SPL token transfers in this transaction, with sender, recipient, token mint address, and amount.
Event types
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
1
Contact support
Reach out to the Knot team to enable Helius webhooks for your agent.
2
Provide your wallet address
Supply your agent’s wallet address so Knot can configure the Helius subscription for your account.
3
Receive events
Knot begins receiving Helius events for your wallet. Balance state and audit logs are updated in real time.
4
React to events
Poll for updated balances or use audit logs to detect incoming transfers and take action.
Native SOL amounts in webhook payloads are denominated in lamports. Divide by 1,000,000,000 to convert to SOL.