Place a signed batch
/order/v1/orders/signed/batchRequired token scope: orders:place_signed.
Submit 1–32 independent signed orders for the authenticated wallet, including orders in different markets. Maximum body: 2 MiB. Each order uses the same signing and expiry rules as single placement.
HTTP 202 contains per-item outcomes, not an all-or-nothing result. Handle accepted, delayed, rejected and unknown items separately using the zero-based index. Rejected items contain failure; accepted, delayed and unknown items contain order-state fields. Results follow input order, which does not establish execution order.
A delayed item has outcome: "delayed", status: "TAKE_ORDER_DELAY" and pending_operation: "SUBMIT". It is waiting before matching, with no confirmed fill or resting order. Keep the original signed request and follow its order ID or hash through reads and account events. Cancellation is refused during the wait. See taker delays.
If you use a generated client or response validator, update it to accept delayed items before submitting batches to markets with taker delays. Treat delayed as a waiting state, not a rejection or a reason to sign a replacement.
Malformed JSON rejects the whole request. Schema errors inside an otherwise valid item fail that item individually. Resolve unknown items before replacing them; see batch orders.
Authorization
bearerAuth Use an agt_ API token with the scope listed on the operation, or a supported browser access token. HTTP authentication is separate from the EIP-712 order signature.
In: header
Request Body
application/json
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/problem+json
application/json
curl -X POST "https://example.com/order/v1/orders/signed/batch" \ -H "Content-Type: application/json" \ -d '{ "orders": [ { "token_id": "string", "side": "BUY", "type": "LIMIT", "time_in_force": "GTC", "price_micro": 1, "shares_micro": 1, "salt": "string", "maker": "string", "chain_token_id": "string", "maker_amount": "string", "taker_amount": "string", "side_u8": 0, "timestamp": "string", "metadata": "string", "builder": "string", "order_hash": "string", "signature": "string" } ] }'{ "results": [ { "index": 0, "outcome": "accepted", "order_id": "f6179e34-1b64-5a10-a662-32f25759da1a", "source": "AGARA", "status": "OPEN", "pending_operation": "NONE", "as_of": "2026-11-04T12:00:00Z", "engine_reference": "12345", "remaining_engine_size": "100" }, { "index": 1, "outcome": "rejected", "failure": { "code": "validation_failed", "title": "Validation failed", "detail": "Invalid order fields.", "recovery": { "strategy": "none" } } }, { "index": 2, "outcome": "unknown", "order_id": "0dc24604-9177-57d1-8b9d-3a9677b0f857", "source": "AGARA", "status": "UNKNOWN", "pending_operation": "SUBMIT", "as_of": "2026-11-04T12:00:00Z", "engine_reference": null, "remaining_engine_size": null }, { "index": 3, "outcome": "delayed", "order_id": "7b8f1f8a-e2c1-5a31-8eab-6b3d134d9305", "source": "AGARA", "status": "TAKE_ORDER_DELAY", "pending_operation": "SUBMIT", "as_of": "2026-11-04T12:00:00Z", "engine_reference": null, "remaining_engine_size": null } ], "as_of": "2026-11-04T12:00:00Z"}Read an order by id GET
Required token scope: orders:read. Read an order belonging to the authenticated wallet. A response can contain a compact order state, or an enriched view with order, markets and state_freshness. Check pending_operation; HTTP 200 can still describe a pending or unknown outcome. Where order is present, check order.is_terminal to distinguish a completed partial FAK from a working partial order. Recent activity can appear in account events before reads. A temporary ORDER_NOT_FOUND does not disprove an uncertain placement; retry unavailable reads without discarding confirmed fills. The as_of time is not a completeness watermark. See [responses, events and reads](/best-practices/order-management#responses-events-and-reads).
Place a signed order POST
Required token scope: orders:place_signed. Submit a pre-signed Agara LIMIT order. Complete wallet setup and approvals first. Sign using the chain and exchange domain described in [pre-signed orders](/api-traders/pre-signed-orders#one-time-setup). The maximum request body is 16 KiB. HTTP 200 provides an order state; it does not imply that the order remains open or that settlement is complete. HTTP 202 with TAKE_ORDER_DELAY acknowledges a wait before matching; it does not confirm a fill or a resting order. HTTP 202 with UNKNOWN leaves the placement unresolved. Keep the exact signed body, hash and any returned ID; read the original order before signing a replacement. A retry is checked against the timestamp or expiry rules again and may be refused after an earlier success. For a delayed order, follow the original ID or hash through reads and account events; cancellation is refused during the wait. See [taker delays](/best-practices/order-management#taker-delays). See the [order management guide](/best-practices/order-management) for cancellation, fills and recovery.