# Create Limit Order

Creates a durable off-chain limit order. The public request shape mirrors `POST /quote` and adds limit-order terms.

**Endpoint:** `POST /api/v1/limit-orders/limit`\
**Auth:** Required (`Authorization: Bearer YOUR_API_KEY`)

## Headers

| Header            | Type   | Description                                                                                                                   | Example                                |
| ----------------- | ------ | ----------------------------------------------------------------------------------------------------------------------------- | -------------------------------------- |
| `Idempotency-Key` | string | Required opaque dedupe token. Use UUIDv4 or ULID. Allowed characters: `A-Z`, `a-z`, `0-9`, `.`, `_`, `:`, `-`. Max 200 chars. | `123e4567-e89b-12d3-a456-426614174000` |

## Request body

| Field           | Type    | Required | Description                       | Example         |
| --------------- | ------- | -------- | --------------------------------- | --------------- |
| `fromChain`     | string  | Yes      | Source chain identifier           | `"arbitrum"`    |
| `toChain`       | string  | Yes      | Destination chain identifier      | `"avax"`        |
| `tokenIn`       | string  | Yes      | Input token identifier            | `"TBTC"`        |
| `tokenOut`      | string  | Yes      | Output token identifier           | `"WETH"`        |
| `amount`        | string  | Yes      | Human amount string               | `"100.00"`      |
| `minAmountOut`  | string  | Yes      | Minimum output amount             | `"1"`           |
| `timeInForce`   | string  | No       | `GTC`, `GTD`, `IOC`, or `FOK`     | `"GTC"`         |
| `expiresAtMs`   | integer | No       | Absolute expiry in ms since epoch | `1745403600000` |
| `expireAfterMs` | integer | No       | Relative expiry in ms             | `86400000`      |
| `network`       | string  | No       | `mainnet` or `testnet`            | `"mainnet"`     |
| `slippageBps`   | integer | No       | Quote-time slippage hint          | `75`            |
| `recipient`     | string  | No       | Recipient address                 | `"0x1234..."`   |
| `route`         | object  | No       | Optional route snapshot           | `{}`            |
| `routeKey`      | string  | No       | Optional route identifier         | `"route_123"`   |

## Example

{% tabs %}
{% tab title="cURL" %}

```bash
curl -X POST 'https://api.gateway.zert.com/api/v1/limit-orders/limit' \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Idempotency-Key: limit-create-001' \
  -d '{
    "timeInForce": "GTC",
    "minAmountOut": "1",
    "fromChain": "arbitrum",
    "toChain": "avax",
    "tokenIn": "TBTC",
    "tokenOut": "WETH",
    "network": "mainnet",
    "amount": "100.00",
    "slippageBps": 75,
    "recipient": "0x1234567890123456789012345678901234567890"
  }'
```

{% endtab %}

{% tab title="Example Response" %}

```json
{
  "data": {
    "limitOrderId": "lim_abc123",
    "status": "open",
    "expiresAtMs": 1745403600000,
    "minAmountOut": "1"
  },
  "meta": {
    "requestId": "req_xyz",
    "timestamp": "2026-04-23T12:00:00.000Z"
  }
}
```

{% endtab %}
{% endtabs %}

## Responses

| Code | Description                               |
| ---- | ----------------------------------------- |
| 200  | Created                                   |
| 400  | Invalid request                           |
| 401  | Unauthorized (missing or invalid API key) |
| 503  | PG unavailable                            |

{% embed url="<https://api.gateway.zert.com/docs>" %}
Zert API — Create Limit Order
{% endembed %}


---

# Agent Instructions: 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:

```
GET https://docs.zert.com/api-reference/limit-orders/limit-order-create.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.