Okapi Okapi
Add to GitHub

Binance USDⓈ-M Futures API · fapi.binance.com

Binance USDⓈ-M Futures API v1 deprecations

The breaking changes Binance USDⓈ-M Futures API announced for its v1 endpoints: 7 of the 10 Okapi tracks.

Already in effect 7

  1. GET /papi/v1/cm/incomeBehaviour change Stopped working
  2. GET /papi/v1/um/incomeBehaviour change Stopped working
  3. GET /dapi/v1/incomeBehaviour change Stopped working
  4. GET /fapi/v1/incomeBehaviour change Stopped working
  5. GET /fapi/v1/accountEndpoint removal Stopped working
  6. GET /fapi/v1/balanceEndpoint removal Stopped working
  7. GET /fapi/v1/positionRiskEndpoint removal Stopped working

Questions

Is the Binance USDⓈ-M Futures API v1 deprecated?

Binance USDⓈ-M Futures API has announced 7 breaking changes to its v1 endpoints: 7 with a shutdown date. Each one's page says what to use instead.

How do I find the calls this hits in my code?

Okapi reads your repository, finds the calls these changes hit and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.

Know before your API calls break.

Okapi finds the calls a breaking change hits in your code and opens the pull request that fixes them.

Add to GitHub