Bybit API
POST /v5/asset/transfer/save-transfer-sub-member endpoint removal
Deprecated, no dateSubscribe to Bybit APIShare
On August 25, 2023, Bybit API deprecated the POST /v5/asset/transfer/save-transfer-sub-member endpoint without a shutdown date. Calls made to this endpoint fail. Because all sub UIDs are automatically enabled for universal transfer, configuring transferable sub UIDs is no longer required.
Calls it hits
POST /v5/asset/transfer/save-transfer-sub-member
What to use instead of these calls
Stop calling the endpoint entirely. Sub UIDs no longer need configuration as transferable before calling POST /v5/asset/transfer/universal-transfer.
In Bybit API's words
You no longer need to configure transferable sub UIDs. Now, all sub UIDs are automatically enabled for universal transfer.
Facts
- API
- Bybit API
api.bybit.com - Kind
- Endpoint removal
- Announced
- August 25, 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 POST /v5/asset/transfer/save-transfer-sub-member 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
GET /v5/broker/earning-recordEndpoint removal Deprecated, no date -
No date
/v5/user/modify-master-apikeyParameter 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.