Bybit API
GET /v5/broker/earning-record endpoint removal
Deprecated, no dateSubscribe to Bybit APIShare
Bybit deprecated GET /v5/broker/earning-record on December 4, 2023, without a shutdown date. Calls targeting this endpoint will fail once it is removed. Bybit API noted that it is replaced by Get Exchange Broker Earning.
Calls it hits
GET /v5/broker/earning-record
What to use instead of these calls
Use GET /v5/broker/earnings-info (Get Exchange Broker Earning) with the exchange broker master account.
In Bybit API's words
deprecated, replaced by Get Exchange Broker Earning
Facts
- API
- Bybit API
api.bybit.com - Kind
- Endpoint removal
- Announced
- December 4, 2023
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Bybit API's own pages
Questions
When does this change take effect?
Bybit API deprecated GET /v5/broker/earning-record without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Bybit 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 Bybit API 5
-
/v5/lending/*Endpoint removal Stopped working -
No date
/v5/user/modify-master-apikeyParameter removal Deprecated, no date -
No date
POST /v5/asset/transfer/save-transfer-sub-memberEndpoint removal Deprecated, no date -
No date
POST /v5/crypto-loan/borrowEndpoint removal Deprecated, no date -
No date
POST /v5/position/set-risk-limitEndpoint 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.