Cancel an order by id
/order/v1/orders/{order_id}Required token scope: orders:cancel.
Cancel the unfilled remainder of this order. No new order signature or request body is required. Completed fills remain valid. Retry an uncertain cancellation using the same order_id.
After ORDER_NOT_OPEN or NOT_FOUND, read the final order state. For PLACE_PENDING or PLACE_OUTCOME_UNKNOWN, resolve the original placement before retrying cancellation. See cancellation strategies.
Authorization
bearerAuth Use an agt_ API token with the scope listed on the operation, or a supported browser access token. HTTP authentication is separate from the EIP-712 order signature.
In: header
Path Parameters
Order UUID.
uuidResponse Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/problem+json
application/json
curl -X DELETE "https://example.com/order/v1/orders/497f6eca-6276-4993-bfeb-53cbbbba6f08"{ "order_id": "f6179e34-1b64-5a10-a662-32f25759da1a", "source": "AGARA", "status": "CANCELLED", "pending_operation": "NONE", "as_of": "2026-11-04T12:00:00Z", "engine_reference": "12345", "remaining_engine_size": "0"}Cancel an order by hash DELETE
Required token scope: orders:cancel. Cancel the unfilled remainder of this order. No new order signature or request body is required. Completed fills remain valid. Retry an uncertain cancellation using the same hash. If cancellation returns NOT_FOUND, look up the hash and cancel using the returned order ID when available. After ORDER_NOT_OPEN or NOT_FOUND, read the final order state. For PLACE_PENDING or PLACE_OUTCOME_UNKNOWN, resolve the original placement before retrying cancellation. See [cancellation strategies](/best-practices/order-management#cancellation-strategies).
Read an order by hash GET
Required token scope: orders:read. Read an order belonging to the authenticated wallet. Use the signed hash when the placement reply was lost. A response can contain a compact order state, or an enriched view with order, markets and state_freshness. Check pending_operation; HTTP 200 can still describe a pending or unknown outcome. Where order is present, check order.is_terminal to distinguish a completed partial FAK from a working partial order. Recent activity can appear in account events before reads. A temporary ORDER_NOT_FOUND does not disprove an uncertain placement; retry unavailable reads without discarding confirmed fills. The as_of time is not a completeness watermark. See [responses, events and reads](/best-practices/order-management#responses-events-and-reads).