Read an order by id
/order/v1/orders/{order_id}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.
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
Path Parameters
Order UUID.
uuidResponse Body
application/json
application/json
application/json
application/json
application/json
application/problem+json
application/json
curl -X GET "https://example.com/order/v1/orders/497f6eca-6276-4993-bfeb-53cbbbba6f08"{ "order_id": "93101167-9065-4b9c-b98b-5d789a3ed9fe", "source": "AGARA", "status": "string", "pending_operation": "SUBMIT", "as_of": "2019-08-24T14:15:22Z", "engine_reference": "string", "remaining_engine_size": "string", "code": "string", "message": "string", "order": { "internal_id": "c13c6907-8dc3-4479-a9ee-0b258d87c410", "exchange": "AGARA", "token_id": "string", "condition_id": "string", "side": "BUY", "type": "string", "price_micro": "string", "original_size_micro": "string", "collateral_amount_micro": "string", "size_matched_micro": "string", "avg_fill_price_micro": "string", "status": "string", "is_terminal": true, "failure": { "code": "string", "title": "string", "detail": "string", "recovery": { "strategy": "string" } }, "expiration": "2019-08-24T14:15:22Z", "created_at": "2019-08-24T14:15:22Z", "cancel_requested_at": "2019-08-24T14:15:22Z" }, "markets": { "property1": { "market_id": "6364d859-8e1b-477a-bacc-de8305a9292b", "market_title": "string", "outcome_name": "string", "logo_url": "string", "event_slug": "string", "state": "string", "neg_risk_id": "string", "display": { "market": {}, "outcome": {} } }, "property2": { "market_id": "6364d859-8e1b-477a-bacc-de8305a9292b", "market_title": "string", "outcome_name": "string", "logo_url": "string", "event_slug": "string", "state": "string", "neg_risk_id": "string", "display": { "market": {}, "outcome": {} } } }, "state_freshness": "LOCAL"}Read an order by hash GET
Required token scope: orders:read. Read an order belonging to the authenticated wallet. Use the signed hash when the placement reply was lost. 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 batch POST
Required 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](/best-practices/order-management#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](/best-practices/order-management#batch-orders).