Cancel Order By ID
We enforce a rate limit of 6000
requests per minute for the createOrder
and cancelOrder
requests.
This limit is shared across all markets and both endpoints.
If you exceed this limit, you will receive a 429 Too Many Requests
response.
Unique Client Request ID
For the current WebSocket request, you can optionally include a unique client request ID in the request body. The same client request ID will be found in the response and is used to match the response to the request. The client request ID must be a UUID.
Order Quantity Fields
In the order
object, quantity
represents the remaining quantity and filledQuantity
represents the cumulative filled quantity.
The two values will add up to the original order quantity.
Conflict And Retry
When you get 409
status code, it means that the order was in the process of being filled at the time of cancellation.
Please retry the cancellation request if you get this status code.
Acknowledgment And Confirmation
When you cancel an order, you will first receive a response to acknowledge that the request has been received. Then you will receive another response to confirm that the order has been successfully cancelled.
There are three differences between these two responses:
Acknowledgment | Confirmation | |
---|---|---|
Body | cancelling order | order cancelled |
Order Status | cancelling | cancelled |
Status Code | 202 | 200 |
URL
This stream can be subscribed per market and you will need to pass in the market in the URL query. See below.
Query params
Example value: ETH-USD
. To get all supported markets, call /api/v1/markets endpoint.
Headers
See Authorization section on how to retrieve authorization token. Once token is received, set Sec-WebSocket-Protocol
headers in the WebSocket handshake request or on connect()
.
Example value (authorization token) :