> For the complete documentation index, see [llms.txt](https://docs.pangolin.exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pangolin.exchange/pangoperps/trading-api/order-management/batch-cancel-orders-by-client-order-id.md).

# Batch Cancel Orders by Client Order ID

Cancel up to 10 orders in one request by client-assigned order IDs.

### Endpoint

**DELETE /v1/client/batch-order?client\_order\_ids={client\_order\_id1},{client\_order\_id2}**

Mainnet: `DELETE https://api.orderly.org/v1/client/batch-order?client_order_ids={client_order_id1},{client_order_id2}`

Testnet: `DELETE https://testnet-api.orderly.org/v1/client/batch-order?client_order_ids={client_order_id1},{client_order_id2}`

Rate limit: 10 requests per second. This endpoint cancels a comma-separated list of up to 10 orders identified by client order IDs. The API key must include the trading scope. An empty list or a list where every ID is invalid returns an invalid client order ID error.

### Authentication headers

* orderly-timestamp — signed-request timestamp in milliseconds.
* orderly-account-id — PangoPerps account ID.
* orderly-key — public API key.
* orderly-signature — request signature.

### Query parameters

| Parameter          | Type   | Required | Description                                                   |
| ------------------ | ------ | -------- | ------------------------------------------------------------- |
| client\_order\_ids | string | Yes      | Comma-separated client order IDs; maximum 10 IDs per request. |

### Example request

```bash
curl --request DELETE \
  --url 'https://api.orderly.org/v1/client/batch-order?client_order_ids=pango-demo-001,pango-demo-002' \
  --header 'orderly-account-id: <account-id>' \
  --header 'orderly-key: <public-api-key>' \
  --header 'orderly-signature: <signature>' \
  --header 'orderly-timestamp: <timestamp-in-ms>'
```

### Successful response

HTTP 200 returns CANCEL\_ALL\_SENT when the batch cancellation request is sent.

```json
{
  "success": true,
  "data": {
    "status": "CANCEL_ALL_SENT"
  },
  "timestamp": 1702989203989
}
```
