Okapi Okapi
Add to GitHub

fapi.binance.com · CryptoSubscribeShare

Binance USDⓈ-M Futures API breaking changes

The breaking changes Binance USDⓈ-M Futures API announced that Okapi tracks: 10 in all.

Do you run the Binance USDⓈ-M Futures API? Make sure your users call it right →

At a glance

API host
fapi.binance.com
Kind
Crypto
Versions with breaking changes
v1 (7), v2 (3)
Breaking changes tracked
3 breaking changes with no date yet and 7 already in effect
Last updated

Deprecated, no date yet 3

  1. No date GET /fapi/v2/accountEndpoint removal Deprecated, no date
  2. No date GET /fapi/v2/balanceEndpoint removal Deprecated, no date
  3. No date GET /fapi/v2/positionRiskEndpoint removal Deprecated, no date

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

Where Okapi reads it

Get notifications

Subscribe to Binance USDⓈ-M Futures API

Hear about each breaking change Binance USDⓈ-M Futures API announces, in your feed reader, calendar or Slack.

1What to follow

Provider
  • Binance USDⓈ-M Futures API

2Where to get it

/breaking-changes/feed.xml

Paste it into Feedly, Inoreader, NetNewsWire or any reader. New changes show up as they're announced.

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