-
Notifications
You must be signed in to change notification settings - Fork 764
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
futuresPositionRisk isn't working in the latest version #919
Comments
Hello @luiztools thanks for reporting it, we will check it. |
I investigated further and when I've changed from v2 to v3 using the code above, the feature that use it stopped working because it needs all positions and related info. I've logged the response with v3 and it was just [], probably because of this statement in the new version: "only symbol that has position or open orders will be returned" For now, I'd prefer to keep using the v2 that works perfectly and returns all positions, but I'll understand if it is ok yo you to change in the main code (I'm using a personal fork). |
@luiztools I will add an option for the users to choose (v2 or v3), but I suspect that v2/ will be deprecared soon. |
@luiztools If you upgrade your node-binance-api to the latest you can now do
or
|
It returns always [] if you use the code below:
futuresPositionRisk: async ( params = {} ) => { return promiseRequest( 'v3/positionRisk', params, { base:fapi, type:'SIGNED' } ); },
To resolve the problem, change it to the following code:
futuresPositionRisk: async ( params = {} ) => { return promiseRequest( 'v2/positionRisk', params, { base:fapi, type:'SIGNED' } ); },
The text was updated successfully, but these errors were encountered: