accountUnsubscribe

accountUnsubscribe tears down one account-change stream that was opened with accountSubscribe on the same WebSocket connection. Its single parameter is the integer subscription id — the result value the server returned in the subscribe ack. On success the server replies result: true and stops pushing accountNotification frames for that id; the socket itself stays open, and any other subscriptions on it keep flowing.

Use it whenever a watch outlives its usefulness while the connection does not: a user navigates away from a wallet view but keeps the app open, a deposit you were waiting for has landed, or you are rotating a large watchlist and want to swap tracked accounts without paying the cost of a reconnect. Explicitly unsubscribing keeps the server-side subscription count down, which matters on connections juggling hundreds of account watches.

Three details are worth knowing. First, the id must belong to the current session — subscription ids are per-connection, so after a reconnect the old ids are meaningless and unsubscribing them returns an error (-32602, invalid subscription id); simply resubscribe instead. Second, unsubscribing is idempotent in effect but not in response: the first call returns true, a repeat call with the same id fails because the subscription no longer exists. Third, you never need to unsubscribe before closing the socket — dropping the connection frees every subscription tied to it automatically. Reserve accountUnsubscribe for surgically stopping one stream while the rest of the session continues.

A stray notification can still arrive in the small window between sending the unsubscribe and receiving the ack; treat unknown subscription ids in incoming frames as ignorable rather than as errors.