OKX API
POST /api/v5/account/set-riskOffset-type endpoint removal
Stopped workingSubscribe to OKX APIShare
On January 17, 2025, POST /api/v5/account/set-riskOffset-type was removed. Calls to this endpoint fail after that day. OKX API marked the feature as offline on the same date.
Calls it hits
POST /api/v5/account/set-riskOffset-type
What to use instead of these calls
Stop calling the endpoint. There is no replacement endpoint documented.
There is no replacement endpoint.
In OKX API's words
API offline - Set risk offset type (POST /api/v5/account/set-riskOffset-type)
Facts
- API
- OKX API
www.okx.com - Kind
- Endpoint removal
- Announced
- January 17, 2025
- Takes effect
- January 17, 2025
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against OKX API's own pages
Questions
When does this change take effect?
Calls to POST /api/v5/account/set-riskOffset-type on OKX API stopped working on January 17, 2025.
What happens to calls after January 17, 2025?
They have failed since January 17, 2025.
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 OKX API 10
-
GET /api/v5/asset/lending-historyEndpoint removal Stopped working -
GET /api/v5/asset/lending-rate-historyEndpoint removal Stopped working -
GET /api/v5/asset/lending-rate-summaryEndpoint removal Stopped working -
GET /api/v5/asset/saving-balanceEndpoint removal Stopped working -
POST /api/v5/asset/purchase_redemptEndpoint removal Stopped working -
GET /api/v5/market/books-liteEndpoint removal Stopped working -
POST /api/v5/asset/convert-dust-assetsEndpoint removal Stopped working -
GET /api/v5/market/open-oracleEndpoint removal Stopped working -
/api/v5/account/fixed-loan/*Endpoint removal Stopped working -
/api/v5/finance/fixed-loan/*Endpoint removal Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.