Cancel Order
Cancel order using order hash or client-side ID.
Last updated
Cancel order using order hash or client-side ID.
Last updated
| Field | Description | Example |
|---|---|---|
| Query Param | Description | Example |
|---|---|---|
| Field | Description | Example |
|---|---|---|
X-API-KEY
ApiKey
"HlkcGxbqBeaF76j4rvPaOasyfPwnkQ6B6DQ6THZWbvrAGxzEdulXQvOKLrRWZLnN"
X-API-SIG
EDDSA Signature, it's the request signing
"0xeb14773e8a07d19bc4fe56e36d041dcb0026bf21e05c7652f7e92160deaf5ea9c4fe56e34773e86d041dcbeb1a07d19b002652f7e92160deaf5e6bf21e05c7a9002652f7e92160deaf5e6bf21e05c7a9eb14773e8a07d19bc4fe56e36d041dcb"
accountId
account ID
orderHash
(Optional) The order hash of submit order response
"0x05a97490e92ded027f65c4bebf3bad63813f4ce8c7255335894566b2eee90206"
clientOrderId
(Optional) The clieetOrderId of submit order
"202003180000 00001010"
hash
The hash identifier set by the user at the time of submission, can use this hash to get the order info
"0x05a97490e92ded027f65c4bebf3bad63813f4ce8c7255335894566b2eee90206"
clientOrderId
The clientOrderId of the submitted order
status
Order status of submit order response Allowable : ['processing', 'processed', 'cancelling', 'cancelled', 'expired', 'failed']
"processing"
isIdempotent
Idempotent of submit transfer response, submit same transfer again idempotent will be true
"false"