Post multiple orders

Batch place up to 100 orders. Each entry succeeds or fails independently — the response array is parallel to the request body. The top-level call returns 200 even when every entry rejects.

POST /orders

xo-orderbook-client-rs

Rust

// Requires an authenticated client. Sign each order, then submit the batch.
let signed_a = client.sign(&signer, order_a).await?;
let signed_b = client.sign(&signer, order_b).await?;
let results = client.post_orders(vec![signed_a, signed_b]).await?;
// Vec<PostOrderResponse> — same length and order as the input.

200

mixed_outcomes

{
  "results": [
    {
      "order_id": "101",
      "fills": 0,
      "resting": true,
      "remaining_size": "100000000",
      "order_hash": "0x0011223344556677889900aabbccddeeff00112233445566778899aabbccddee",
      "error": null
    },
    {
      "order_id": "102",
      "fills": 1,
      "resting": false,
      "remaining_size": "0",
      "order_hash": "0x1122334455667788990011223344556677889900aabbccddeeff112233445566",
      "error": null
    },
    {
      "order_id": null,
      "fills": null,
      "resting": null,
      "remaining_size": null,
      "order_hash": null,
      "error": "insufficient balance: required 200000000, available 50000000"
    }
  ]
}

Body

application/json

Maximum array length: 100

order · object · required

EIP-712 signed order. Wire fields are camelCase. Sign over domain name="XO Market CLOB", version="1", chainId=<XO chain id>, verifyingContract=<CTF Exchange address>. XO Privy/ZeroDev smart accounts use signatureType = 3; direct EOA integrations use signatureType = 0.

Orders do not carry a fee rate. Fetch the market category rate with GET /fee-rate and see the Fees guide for the conviction curve. Legacy wire keys taker and feeRateBps are ignored on parse and must not be used for signing (the typehash changed).

Show child attributes

orderType · enum<string> · required

• GTC - Good-Till-Cancel; rests on the book until filled or cancelled.
• GTD - Good-Till-Date; requires non-zero expiration in the signed order.
• FOK - Fill-Or-Kill; fills the entire signed takerAmount (BUY) / makerAmount (SELL) at the signed price or rejects with no fills.
• FAK - Fill-And-Kill (a.k.a. IOC); fills as much as the book supports at the signed price; cancels any unfilled remainder.

Market-style execution. There is no dedicated MARKET value. Submit a signed CTFOrder at an aggressive cap price (e.g. 0.99 for BUY, 0.001 for SELL), then choose FAK for immediate partial fill or FOK for all-or-nothing execution. The matching logic can also use economically compatible YES/NO liquidity.

Available options: GTC, FAK, FOK, GTD

postOnly · boolean · default: false

Envelope flag — not part of the signed EIP-712 order. When true, the order must rest without taking any liquidity. The engine rejects it (HTTP 400) if it would match at placement via COMPLEMENTARY, MINT, or MERGE.

Requires orderType of GTC or GTD. FAK / FOK with postOnly: true returns {"error": "postOnly orders must use orderType GTC or GTD"}. A crossing GTC/GTD returns {"error": "post-only order would cross resting liquidity"}.

Omitted or false is a normal order.

Response

200

application/json

OK

results · object[]

Show child attributes