POST /exchange/v1/private/create-order → endpoint removal
Crypto.com Exchange API
Stopped working
On December 17, 2025, support for the ref_price body parameter on POST /exchange/v1/private/create-order will end. Requests that continue sending this parameter to the endpoint will fail. Trigger order management is being moved to the Advanced Order Management API.
Calls it hits
POST /exchange/v1/private/create-orderbody parameter ref_price
What to use instead of these calls
Create trigger orders such as STOP_LOSS, STOP_LIMIT, TAKE_PROFIT, and TAKE_PROFIT_LIMIT with ref_price using private/advanced/create-order. Cancel these orders using private/advanced/cancel-order.
In Crypto.com Exchange API's words
The current trigger order creation/cancellation will be migrated to Advanced Order Management API.
Facts
- API
- Crypto.com Exchange API
api.crypto.com - Kind
- Endpoint removal
- Takes effect
- December 17, 2025
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Crypto.com Exchange API's own pages
Questions
When does this change take effect?
Calls to POST /exchange/v1/private/create-order, body parameter ref_price on Crypto.com Exchange API stopped working on December 17, 2025.
What happens to calls after December 17, 2025?
They have failed since December 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.
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.