> For the complete documentation index, see [llms.txt](https://docs.nexus.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexus.xyz/api-reference/trading/create-orders-batch.md).

# POST /orders/batch

Submit multiple orders.

`operationId`: `createOrdersBatch` · CCXT method: `createOrders` · Rate-limit class: `trading`

**Authentication:** `hmacAuth`.

Submit multiple orders in one request. Orders are processed sequentially and non-atomically: an early order consuming margin can cause a later order in the same batch to fail, and per-order failures do not abort the batch. The response array preserves request order with a per-order success or error result.

**Weighted by batch size.** This call costs `1 + floor(order_count / 40)` units of the trading-action budget, so up to 40 orders cost the same as a single order and every further 40 adds a unit. Batching is therefore cheaper than the equivalent individual submits, and the cost of one call is capped at one second of tokens so a large batch can never be permanently unsatisfiable. See “Rate limits” in the API description.

## Request body

**Required.** `application/json`. **The contract declares no schema for this body** — only the example below, so a generated client gets an untyped body here.

## Responses

| Status | Body                                                                   | Meaning                                                                                                                                                   |
| ------ | ---------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `201`  | array of [`OrderResult`](/api-reference/guides/schemas.md#orderresult) | Per-order results, in request order. Returned with status 201 for the batch as a whole even when individual entries failed; inspect each entry's `error`. |
| `401`  | — *(no schema declared)*                                               | —                                                                                                                                                         |
| `403`  | — *(no schema declared)*                                               | —                                                                                                                                                         |
| `429`  | — *(no schema declared)*                                               | —                                                                                                                                                         |

## Example

```bash
curl -X POST 'https://exchange.nexus.xyz/api/exchange/orders/batch' \
  -H 'X-API-Key: nx_7f3a1b...' \
  -H 'X-Timestamp: 1776033911836' \
  -H 'X-Signature: <hmac-sha256>' \
  -H 'Content-Type: application/json'
```

***

<sub>Generated from</sub> <sub></sub><sub>`eng/apps/exchange/api/openapi.json`</sub> <sub></sub><sub>(spec</sub> <sub></sub><sub>`0.9.27`</sub><sub>). Do not edit by hand — regenerate with</sub> <sub></sub><sub>`python3 product/docs/tools/api-reference/generate.py`</sub><sub>. Hand-authored context lives in the Guides pages.</sub>


---

# 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://docs.nexus.xyz/api-reference/trading/create-orders-batch.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.