Skip to main content

voteUnsubscribe

Unsubscribe from vote notifications

Common use cases
Subscription cleanup on shutdownFree server resources when stopping vote monitoring. Always call voteUnsubscribe when terminating research sessions or validator analysis tools.
Subscription managementCancel vote subscription when switching monitoring modes or RPC providers. Returns false if subscription ID invalid or already unsubscribed.

Parameters

subscriptionId (integer, required)

subscription id to cancel

Request

wscat -c wss://solana-mainnet.api.syndica.io -x '{
"jsonrpc": "2.0",
"id": 1,
"method": "voteUnsubscribe",
"params": [
0
]
}'
Network Selection

Replace mainnet with devnet in the URL to query devnet instead.

Response

{
"jsonrpc": "2.0",
"result": true,
"id": 1
}

Response Fields

Return value: boolean

unsubscribe success message

FAQ and Troubleshooting

What happens if I don't call voteUnsubscribe?

The subscription remains active until WebSocket closes, consuming server resources. Always explicitly unsubscribe for proper cleanup.

Can I reuse a subscription ID after unsubscribing?

No. Each subscription ID is unique per WebSocket connection. Create new subscription with voteSubscribe if needed.

What does the boolean result mean?

true indicates successful unsubscription, false means the subscription ID wasn't found (already unsubscribed or never existed).

voteSubscribe
Creates vote subscription. Always paired with voteUnsubscribe; both are unstable methods requiring same validator flag for proper vote monitoring lifecycle.

slotUnsubscribe
Cancels slot subscription. Similar unsubscribe pattern; both follow standard WebSocket subscription lifecycle where unsubscribe methods take subscription ID and return boolean.

External Resources