Binance USDⓈ-M Futures API
GET /fapi/v1/balance endpoint removal
Stopped workingSubscribe to Binance USDⓈ-M Futures APIShare
On July 15, 2023, the GET /fapi/v1/balance endpoint was removed and stopped working. Following that date, requests sent to this endpoint fail. Binance announced this deprecation on June 28, 2023, stating that the endpoint would no longer be supported.
Calls it hits
GET /fapi/v1/balance
What to use instead of these calls
Call GET /fapi/v2/balance instead.
In Binance USDⓈ-M Futures API's words
The following endpoints will no longer be supported from 2023-07-15:
Facts
- API
- Binance USDⓈ-M Futures API
fapi.binance.com - Kind
- Endpoint removal
- Announced
- June 28, 2023
- Takes effect
- July 15, 2023
- 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?
Calls to GET /fapi/v1/balance on Binance USDⓈ-M Futures API stopped working on July 15, 2023.
What happens to calls after July 15, 2023?
They have failed since July 15, 2023.
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/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/balanceEndpoint removal Deprecated, no date -
No date
GET /fapi/v2/positionRiskEndpoint removal Deprecated, no date
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.