support /fapi/v3/positionRisk #644
Conversation
xyq-c-cpp
commented
Dec 5, 2024
xyq-c-cpp
commented
- support /fapi/v3/positionRisk, close Request upgrade NewGetPositionRiskService V2 => V3 #602
| func (c *Client) NewGetPositionRiskV2Service() *GetPositionRiskV2Service { | ||
| return &GetPositionRiskV2Service{c: c} | ||
| } | ||
|
|
There was a problem hiding this comment.
Is there any reason to keep this V2 service? In my opinion, we only need the latest version of each service.
There was a problem hiding this comment.
Binance still provides this interface, so I have kept it. Of course, I can also keep only the V3 version @adshao
There was a problem hiding this comment.
Binance still provides this interface, so I have kept it. Of course, I can also keep only the V3 version @adshao
OK, that's fine, we can keep it as long as binance provides both v2/v3 interfaces.
There was a problem hiding this comment.
@xyq-c-cpp @adshao
The second version should definitely be kept, as it allows you to view the leverage and margin type for each position at once in one query, while in version 3 you can't do that - you will have to make a query /fapi/v1/symbolConfig for each open position to view the current leverage, which will require much more queries and will use up the rate limit much faster.
