Binance USDⓈ-M Futures API
GET /fapi/v2/balance endpoint removal
Deprecated, no dateSubscribe to Binance USDⓈ-M Futures APIShare
GET /fapi/v2/balance has been deprecated without a shutdown date. Binance announced on July 24, 2024, that the endpoint will be deprecated in the coming months, with the exact date to be announced later. Once fully removed, calls to this endpoint will fail.
Calls it hits
GET /fapi/v2/balance
What to use instead of these calls
Call GET /fapi/v3/balance instead.
In Binance USDⓈ-M Futures API's words
The following endpoints will be deprecated in the coming months (exact date to be announced later). Please switch to the new endpoints listed above:
Facts
- API
- Binance USDⓈ-M Futures API
fapi.binance.com - Kind
- Endpoint removal
- Announced
- July 24, 2024
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Binance USDⓈ-M Futures API's own pages
Questions
When does this change take effect?
Binance USDⓈ-M Futures API deprecated GET /fapi/v2/balance without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Binance USDⓈ-M Futures API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Binance USDⓈ-M Futures API 9
-
GET /fapi/v1/accountEndpoint removal Stopped working -
GET /fapi/v1/balanceEndpoint removal Stopped working -
GET /fapi/v1/positionRiskEndpoint removal Stopped working -
GET /dapi/v1/incomeBehaviour change Stopped working -
GET /fapi/v1/incomeBehaviour change Stopped working -
GET /papi/v1/cm/incomeBehaviour change Stopped working -
GET /papi/v1/um/incomeBehaviour change Stopped working -
No date
GET /fapi/v2/accountEndpoint removal Deprecated, no date -
No date
GET /fapi/v2/positionRiskEndpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.