fix(futures): use listenKey query param for user data WebSocket#812
Merged
carlosmiei merged 1 commit intoccxt:masterfrom May 5, 2026
Merged
fix(futures): use listenKey query param for user data WebSocket#812carlosmiei merged 1 commit intoccxt:masterfrom
carlosmiei merged 1 commit intoccxt:masterfrom
Conversation
sc0Vu
approved these changes
Apr 28, 2026
Contributor
sc0Vu
left a comment
sc0Vu
left a comment
There was a problem hiding this comment.
@carlosmiei the new URL works for me. Also we've used ?listenKey in other functions.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Background
Binance has changed USDS-M futures user data WebSocket URLs. The legacy pattern no longer receives user data over the WebSocket; clients must migrate to the new private endpoint and pass
listenKeyas a query parameter instead of a path segment.Reference: Important WebSocket Change Notice – Compatibility & migration guidance
Changes
WsUserDataServeinv2/futures/websocket_service.go: build the URL as{private/ws base}?listenKey=<key>instead of{private/ws base}/<key>.