Cancel Order
Trading
Cancel Order
Cancel an open order by internal UUID. HMAC tokens require the trading scope; delegated cancellation also requires delegated_signing.
DELETE
Cancel Order
This endpoint cancels by internal
orderId. To cancel by either orderId or clientOrderId, use Cancel Order (Combined).To cancel multiple orders at once, use Batch Cancel Orders (Combined), Cancel Orders (Batch), or Cancel All.
Authentication and delegation
Use a scoped API token with HMAC signing and thetrading scope. To cancel for a partner sub-account, add ?onBehalfOf=<subProfileId>; the target must belong to the authenticated partner and the token must also have delegated_signing. Include the query string in the HMAC-signed path.
Cancellation behavior
A delayed order can be canceled before execution, including a delayed FAK or FOK order. That path returnsDelayed order canceled successfully. Immediate FAK/FOK orders are generally terminal and no longer cancellable.
The endpoint distinguishes:
404 Order not foundwhen the internal ID does not exist;401 Unauthorizedwhen the order belongs to another profile;400 Market has already been resolvedfor a resolved market; and400 Order not found or already canceledwhen the order can no longer be canceled.
Authorizations
Scoped API token with HMAC-SHA256 signing. Requires three headers: lmts-api-key (token ID), lmts-timestamp (ISO-8601), lmts-signature (Base64-encoded HMAC). See Authentication docs for details.
Path Parameters
Unique identifier of the order to be cancelled
Pattern:
^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-4[0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}$Example:
"6f52b6d2-6c9e-4a5c-8a4f-28ab4b7ff203"
Query Parameters
Partner sub-account profile ID. Requires delegated_signing in addition to trading.
Required range:
x >= 1Example:
326
Response
Order successfully cancelled
Confirmation message for the cancelled order
Available options:
Order canceled successfully, Delayed order canceled successfully Example:
"Order canceled successfully"