Get hub status

GET /v1/status/{orderId} The hub’s own lifecycle view, from its event projection. The status door for open-flow orders; it also answers for an openFor order by its hubOrderId.

Item	Value
Route key	`infinityOrderStatus`
Credential	API key or project id; your organization’s orders only
`X-Infinity-Subject`	not read: the hub does not scope this view to one of your users

One of the hub’s three status views — the hub’s own projection. Which view answers which question: Order lifecycle.

Request

Path parameters

Param	Rules	Meaning
`orderId`	exactly 64 lowercase hex characters, no `0x` (the `POST /order` `orderId` or an openFor `hubOrderId`)	anything else is `EIN0001` reference `orderId`

Response

data (OrderStatus):

Field	Type	Meaning
`orderId`	string	echoed
`domains`	object	eight fixed keys, each `{state, terminal, updatedAt?, finality?}` — below
`lastEventSeq`	integer	monotonic poll cursor (0 for an order the projection has not reached yet)
`asOf`	timestamp	when the hub read the view, not when it answered: the view is cached for 2 seconds, and reads inside that window repeat the same `asOf`
`watermarks`	object	per chain domain, `{blockNumber, blockHash?, updatedAt}` — the block up to which the projection is complete for that chain. A chain with none published is absent (never block 0). A chain’s watermark moves only when the reconciler processes a new observation on that chain, about 1–2 minutes (one sweep window) after it, so on a quiet chain it can be far behind the observer watermarks of `GET /onchain/{orderId}/fill`; one chain’s `updatedAt` has also been seen 2 hours off (known issue). Omitted when empty

The eight domains and their states (an empty state means not reached):

Domain	States	Terminal
`intent`	`CREATED`	`CREATED`
`sourceTx`	`DEPOSIT_FINALIZED`	`DEPOSIT_FINALIZED`
`providerCustody`	`DISPATCHED`	—
`receiver`	`OPEN`, `USER_PAID`, `BACKSTOP_PAID`, `RECOVERY_ONLY`	`USER_PAID`, `RECOVERY_ONLY`
`delivery`	`DETECTED`, `FINALIZED`	`FINALIZED`
`guarantee`	`RESERVED`, `ACTIVE`, `RELEASED`, `EXPIRED`, `BACKSTOP_PAID`	`RELEASED`, `EXPIRED`, `BACKSTOP_PAID`
`recovery`	`ACTIVE`, `ESCALATED`, `RECOVERING`, `SURPLUS`, `CLOSED`	—
`solverSettlement`	`FILLED`, `SETTLED`, `REFUNDED`	`SETTLED`, `REFUNDED`

updatedAt can appear on intent (only while lastEventSeq is 0) and on delivery; finality (PENDING, FINALIZED, ORPHANED) on sourceTx and delivery.

Behavior

Owner-scoped. The owner is the organization named on the order’s creation record. An order another organization created answers EIN0009 with the same reference as an unknown id, including when the view is served from the cache. An id with no creation record answers EIN0009 to every caller. The view is not scoped by X-Infinity-Subject: any call of your organization reads any of its orders, so a backend that serves several users answers this route for the user’s own orders only. An on-chain order id is refused before that, as EIN0001 orderId, because it carries 0x: use the on-chain views (Get on-chain fill, Get escrow order) for those. The view is cached for 2 seconds; staleness can under-report progress and never gates money. Uncovered orders do not progress. An order whose quote carries executionClass PROVIDER_NATIVE_UNCOVERED, the class of every lane POST /order/openfor accepts, has no admissible domain transitions after creation. Its view reads intent CREATED with the other seven domains empty for the order’s whole life, even after the order has filled and settled on chain (known issue). Follow openFor orders with GET /order/{orderId}/status and the on-chain views; this route gives the intent record.

Errors

Code	When
`EIN0001`	`orderId`
`EIN0009`	no such order, or not yours
`EIN0051`	projection, creation-record or watermark read unavailable

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/status/a1c662328ee36c035986071fdca2997c167288c9da362f7d540ff102dfedf4c2 \
  -H "x-api-key: $HUB_API_KEY"

Response

Illustrative values; formats follow the Response table. Same quote as the openFor pages for id-consistency: one quote completes through one flow, so this order’s orderId is the hubOrderId POST /order/openfor returned for it.

{
  "success": true,
  "request_id": "41526374-8596-47c1-9c2d-3e4f50617283",
  "data": {
    "orderId": "a1c662328ee36c035986071fdca2997c167288c9da362f7d540ff102dfedf4c2",
    "domains": {
      "delivery": { "state": "", "terminal": false },
      "guarantee": { "state": "", "terminal": false },
      "intent": { "state": "CREATED", "terminal": true },
      "providerCustody": { "state": "", "terminal": false },
      "receiver": { "state": "", "terminal": false },
      "recovery": { "state": "", "terminal": false },
      "solverSettlement": { "state": "", "terminal": false },
      "sourceTx": { "state": "", "terminal": false }
    },
    "lastEventSeq": 1,
    "asOf": "2026-09-22T12:01:00Z",
    "watermarks": {
      "eip155-1": { "blockNumber": 7031, "blockHash": "0xa820bbc72094336fc3cc07d3e9bb087f78edcdd2476bc4823b9ec53ad0d13e96", "updatedAt": "2026-09-22T11:59:40Z" },
      "eip155-56": { "blockNumber": 7036, "blockHash": "0xcd1e34bf5a23730c5eae2971908e272f8a93aaa28025283b201f8b439ff05658", "updatedAt": "2026-09-22T11:59:40Z" }
    }
  }
}

This order’s quote carries executionClass PROVIDER_NATIVE_UNCOVERED, so the view stays like this for the order’s whole life, fill and settlement included (Behavior). intent has no updatedAt because the projection already holds the order (lastEventSeq 1). The watermarks are the projection’s: at the same moment the observers are at block 7061 on eip155-56 (GET /onchain/{orderId}/fill).

// client: your InteropClient (see /infinity-interop/sdk/installation)
const view = await client.api.getHubOrderStatus(created.orderId);

Get started

Core concepts

Resources

API reference

SDK

SDK reference

Request

Path parameters

Response

Behavior

Errors

Example

Response

See also

​Request

​Path parameters

​Response

​Behavior

​Errors

​Example

​Response

​See also

Request

Path parameters

Response

Behavior

Errors

Example

Response

See also