List orders

GET /v1/orders The openFor submissions your organization made under the X-Infinity-Subject you send — one of your users’, or all of them when every call shares one subject — each joined to what the hub’s observers recorded on chain.

Item	Value
Route key	`infinityOrdersList`
Credential	API key only (a project id is refused `EPX0003`)
`X-Infinity-Subject`	required: only the orders placed under it are listed

When every call of yours shares one subject (the SDK’s ownership scope sends default), the listing under it holds every order of your organization, whichever of your users placed it. Never hand it to a browser unfiltered. To show one user their history, name each user in the subject (Authentication — your users), or build it on your server from your own record of who placed which order; the SDK’s createInteropProxy does either (Partner backend).

Request

Headers

Header	Rules	Meaning
`X-Infinity-Subject`	required; `^[A-Za-z0-9._@+~-]{1,128}$`	the subject to list: only the orders placed under it are listed, and the page echoes it in `subject`

Query parameters

Param	Type	Rules	Meaning
`since`	RFC 3339 timestamp	optional	strictly-after cursor: pass the previous page’s last `submittedAt`. Absent = from the beginning
`limit`	integer	optional, > 0	page size, default 100; values above 500 are capped at 500

Pages are ordered by submittedAt, ascending. Records are keyed by orderId — deduplicate by id if you choose an overlapping cursor. Open-flow registrations (POST /order) are not listed.

Response

data (OrdersList):

Field	Type	Meaning
`orders[]`	array	always present (possibly empty); entries below
`subject`	string	the `X-Infinity-Subject` this page was scoped to, verbatim. Refuse a page whose `subject` is not exactly the one you sent

Each entry (OrderListEntry):

Field	Type	Meaning
`orderId`	string	the aggregator id — the status handle
`hubOrderId`	string	the hub’s alias
`quoteId`, `quoteRequestId`	string	the quote it was submitted against
`state`	string	the initial upstream state at submission — never updated here
`submittedAt`	timestamp	the paging cursor
`createdAt`	timestamp	the same instant as `submittedAt`
`onchainOrderId`	string	the on-chain id — the key `chain` was joined by and the key for the on-chain views. Recorded at submission, so it is present from the first listing, before anything is observed; a row older than the field carries the `orderId`
`onchainOrderIdSource`	string	`verified` (the hub’s own recompute agreed with the upstream) or `upstream` (the upstream’s answer alone); absent on older rows
`swapInput`	object	token-in orders only: `{assetRef, amountMax}` — what the user paid with
`quote`	object	the terms as quoted: `{sourceChain, destChain, sourceAsset, destAsset, amountIn, amountOut, recipient, swapType}` — present from the first listing on orders submitted since the field was added; absent on older rows
`chain`	object	the on-chain facts — absent until something is observed (a fact, not an error)

chain (OrderChainFacts):

Field	Type	Meaning
`status`	string	derived at read time: `AWAITING_OPEN`, `OPEN`, `PARTIALLY_FILLED`, `FILLED`, `SETTLED`, `REFUNDED`, `EXPIRED`. Terminal: `SETTLED`, `REFUNDED`. `EXPIRED` (an output missed its fill deadline; render it as failed) is not: no fill can complete the order any more, but the escrow can be refunded once `refundableAfter` passes, and the entry then reads `REFUNDED`
`refundEligible`	boolean	advisory estimate: the open was observed, the order is neither settled nor refunded, and now is past `refundableAfter`
`refundEligibilitySource`	string	always `stored_projection` — undated stored observations, not live contract state
`refundRequiresOnchainCheck`	boolean	always `true` — verify the live contract before offering or sending a refund
`expires`	timestamp	the escrow’s expiry; absent when the open was disclosed id-only
`fillDeadline`	timestamp	the escrow’s fill deadline; absent likewise
`refundableAfter`	timestamp	the deadline in force: `expires`, or a later deadline a refund extender set; absent when `expires` is unknown
`refundDeadline`	timestamp	the deadline an extender last set; absent when nobody extended the order
`user`	string	the escrow’s user — who a refund pays. Absent until the Open is observed (a fill can be observed first)
`sourceChain`, `sourceTxHash`	string	the origin escrow’s chain and Open transaction. Absent until the Open is observed
`inputs[]`, `outputs[]`	array	always present: `{chainDomain, token, symbol?, decimals?, amount, recipient?, fillTxHash?, paidAmount?}`. `symbol`/`decimals` come from the catalog; `recipient` is on outputs; `fillTxHash` and `paidAmount` (what the fill actually paid — differs from `amount` on an auctioned output) appear once a fill is observed

Errors

Code	When
`EIN0001`	`since`, `limit`, `x-infinity-subject` (missing, or outside the rule)
`EIN0050` / `EIN0051`	availability — the whole page fails

The gateway’s own refusals — a refused credential, a route not open to it, a rate limit, the hub unreachable or too slow — can come back from every route, with an EPX code and a real HTTP status (Errors — gateway codes); EIN0049 (internal, scrubbed) can come back from any route.

Example

curl -sS "https://proxy-api.infinimesh.net/v1/orders?limit=100" \
  -H "x-api-key: $HUB_API_KEY" \
  -H "X-Infinity-Subject: default"

Response

Illustrative values; formats follow the Response table. The call used one shared subject, default, which the page echoes.

{
  "success": true,
  "request_id": "52637485-96a7-48d2-ad3e-4f5061728394",
  "data": {
    "orders": [
      {
        "orderId": "0x8c7f293ae9851d2919e1543d0268483a0636bef9417240b0aa15258c508e32b9",
        "hubOrderId": "a1c662328ee36c035986071fdca2997c167288c9da362f7d540ff102dfedf4c2",
        "quoteId": "b9760d500009ec356eb2fc720c32cb77b8b0420a8e2b2deb6a97ce63ba64fb58",
        "quoteRequestId": "01M34FSW4R9F2C4E7A1B3D5F80",
        "state": "created",
        "submittedAt": "2026-09-22T12:00:20Z",
        "onchainOrderId": "0x8c7f293ae9851d2919e1543d0268483a0636bef9417240b0aa15258c508e32b9",
        "onchainOrderIdSource": "upstream",
        "createdAt": "2026-09-22T12:00:20Z",
        "quote": {
          "sourceChain": "eip155-1",
          "destChain": "eip155-56",
          "sourceAsset": "weth",
          "destAsset": "wbnb",
          "amountIn": "1000000000000000",
          "amountOut": "32548366596169380000",
          "recipient": "0xf39fd6e51aad88f6f4ce6ab8827279cfffb92266",
          "swapType": "exact-input"
        },
        "chain": {
          "status": "FILLED",
          "refundEligible": false,
          "refundEligibilitySource": "stored_projection",
          "refundRequiresOnchainCheck": true,
          "expires": "2100-01-01T00:06:40Z",
          "fillDeadline": "2100-01-01T00:01:40Z",
          "refundableAfter": "2100-01-01T00:06:40Z",
          "user": "0xf39fd6e51aad88f6f4ce6ab8827279cfffb92266",
          "sourceChain": "eip155-1",
          "sourceTxHash": "0x7e3a9c1b5d2f8e4a0c6b3d9f1e7a5c2b8d4f0a6e3c9b1d7f5a2e8c4b0f6d3a9e",
          "inputs": [
            { "chainDomain": "eip155-1", "token": "0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2", "symbol": "WETH", "decimals": 18, "amount": "1000000000000000" }
          ],
          "outputs": [
            { "chainDomain": "eip155-56", "token": "0xbb4cdb9cbd36b01bd1cbaebf2de08d9173bc095c", "symbol": "WBNB", "decimals": 18, "amount": "32548366596169380000", "recipient": "0xf39fd6e51aad88f6f4ce6ab8827279cfffb92266", "fillTxHash": "0x4b8d2f6a1e9c3b7d5f0a8e2c6b4d9f1a3e7c5b0d8f2a6e4c1b9d3f7a5e0c8b2d", "paidAmount": "32548366596169380000" }
          ]
        }
      }
    ],
    "subject": "default"
  }
}

swapInput is absent (not a token-in order); refundDeadline is absent (nobody extended the deadline); inputs[] never carries recipient/fillTxHash/paidAmount. For one of your users, send their subject instead. The page then lists only their orders, and its data carries "subject": "user-42":

curl -sS "https://proxy-api.infinimesh.net/v1/orders?limit=100" \
  -H "x-api-key: $HUB_API_KEY" \
  -H "X-Infinity-Subject: user-42"

// client: your InteropClient (see /infinity-interop/sdk/installation)
const page = await client.api.listOrders({ limit: 100 }); // under hubTransport's subject, "default" unless set
const theirs = await client.api.listOrders({ limit: 100 }, { subject: "user-42" });

Get started

Core concepts

Resources

API reference

SDK

SDK reference

Request

Headers

Query parameters

Response

Errors

Example

Response

See also

​Request

​Headers

​Query parameters

​Response

​Errors

​Example

​Response

​See also

Request

Headers

Query parameters

Response

Errors

Example

Response

See also