> For the complete documentation index, see [llms.txt](https://abcc-docs.gitbook.io/api/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://abcc-docs.gitbook.io/api/spot-trade/cancel-order.md).

# Cancel Order

## Cancel Order

<mark style="color:green;">`POST`</mark> `https://api.abcc.com/api/v1/exchange/orders/:order_id/cancel`

#### Path Parameters

| Name      | Type    | Description |
| --------- | ------- | ----------- |
| order\_id | integer | Order ID    |

#### Request Body

| Name        | Type   | Description                                                |
| ----------- | ------ | ---------------------------------------------------------- |
| tonce       | string | Timestamp of the current time in milliseconds (Unix epoch) |
| signature   | string |                                                            |
| access\_key | string |                                                            |

**OUTPUT EXPLANATION**

| Parameter         | Type    | Explain                                |
| ----------------- | ------- | -------------------------------------- |
| id                | Integer | ID                                     |
| created\_at       | String  | order time                             |
| market\_code      | String  | The only code for the market           |
| side              | String  | Buy and sell type                      |
| state             | String  | status                                 |
| ord\_type         | String  | Order type                             |
| price             | String  | Order price                            |
| avg\_price        | String  | The average price of transactions      |
| volume            | String  | Initial pending order volume           |
| remaining\_volume | String  | The remaining amount of pending orders |
| executed\_volume  | String  | Executed pending order volume          |
| trades\_count     | Integer | Number of transactions                 |

SIDE

| Parameter | Type   | Explanation |
| --------- | ------ | ----------- |
| Buy       | String | Buy         |
| Sell      | String | Sell        |

STATE

| Parameter | Type   | Explanation           |
| --------- | ------ | --------------------- |
| Wait      | String | Pending order         |
| Done      | String | Completed transaction |
| Cancel    | String | Canceled              |

ORD\_TYPE

| Parameter | Type   | Explanation  |
| --------- | ------ | ------------ |
| limit     | String | Limit order  |
| market    | String | Market order |

**Notice**

* Canceling a pending order is an asynchronous operation. The successful return of the API only means that the cancellation request has been successfully submitted and the server is processing it. It does not mean that the order has been canceled.
* When your pending order has unprocessed trade transactions, or the cancellation request queue is busy, the order will be delayed for cancellation


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://abcc-docs.gitbook.io/api/spot-trade/cancel-order.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.