# ref_price on POST /exchange/v1/private/create-order stops working

Calls to POST /exchange/v1/private/create-order, body parameter ref_price on Crypto.com Exchange API stopped working on December 17, 2025.

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.

## What to use instead

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.

- API: Crypto.com Exchange API (api.crypto.com)
- Kind: Endpoint removal
- Takes effect: December 17, 2025
- Calls after that day: fail
- Calls it hits: `POST /exchange/v1/private/create-order`, `body parameter ref_price`
- Source: [Announcement](https://exchange-developer.crypto.com/exchange/v1/docs/api/rest-breaking-change-schedule)
- Verified: October 26, 2026, against Crypto.com Exchange API's own pages
- Page: https://www.okapi.bot/providers/crypto-com-exchange-api/breaking-changes/ref-price-on-post-exchange-v1-private-create-order-stops-working/

## Crypto.com Exchange API's words

> The current trigger order creation/cancellation will be migrated to Advanced Order Management API.

Okapi finds the calls this change hits in your repo and opens the pull request with the fix: https://github.com/apps/okapi-agent