Cancel multiple orders in batch
Trading
Cancel Orders (Batch)
Cancel a non-empty list of internal UUIDs from one market. HMAC tokens require the trading scope; delegated cancellation also requires delegated_signing. This legacy endpoint has no batch maximum.
POST
Cancel multiple orders in batch
This endpoint cancels multiple orders by internal
orderIds only. Send { "orderIds": [...] } with at least one UUIDv4 order ID. This legacy endpoint has no documented maximum batch size, but all orders that resolve must belong to one market.
To cancel by either
orderIds or clientOrderIds, use Batch Cancel Orders (Combined).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.
Results
200 OKreturns the canceled order IDs.207 Multi-Statusreturns bothcanceledand normalizedfailedrecords.400 Bad RequestwithFailed to cancel any ordersmeans every attempted cancellation failed.404 Orders not foundmeans none of the supplied IDs resolved.
ORDER_NOT_FOUND with Order not found or already canceled, or UNKNOWN_ERROR with Failed to cancel order. Cancellation remains available in normal, post_only, and cancel_only; disabled returns 425 Too Early.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.
Query Parameters
Partner sub-account profile ID. Requires delegated_signing in addition to trading.
Required range:
x >= 1Example:
326
Body
application/json
Array of order IDs to be cancelled in a single batch operation
Minimum array length:
1Pattern:
^[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: