Get on-chain fill

GET /v1/onchain/{orderId}/fill What the hub’s own observers saw on the chains, keyed by the on-chain order id. Unlike the status reads, these routes are not scoped to your organization (chain data is public, and a refund may be sent from another device than the one that ordered). They take your secret key or your project id, so a web page can follow the orders it submits on chain itself.

Item	Value
Route key	`infinityOnchainFill`
Credential	API key or project id

The id format matters, and it is not validated. Observations are stored under 0x + 64 lowercase hex. Any other spelling (uppercase, no 0x) is not an error: it answers 200 with no facts and a watermark for every known chain, which reads exactly like “not filled yet”, so the withdraw rule would offer a withdraw for an order that is in fact filled (known issue). Pass onchainOrderId exactly as the hub serves it, and check the format before calling.

Never send an empty id: /onchain//fill is not a route.

Request

Path parameters

Param	Rules	Meaning
`orderId`	`0x` + 64 lowercase hex (not validated)	the on-chain order id

Response

data (OnchainFill):

Field	Type	Meaning
`onchainOrderId`	string	echoed; always present
`open`	EventFact	the escrow Open — absent while unobserved
`filled`	EventFact	the destination fill — absent while unobserved
`settled`	EventFact	the settlement — gated on chain by the attestation, so an observed settle is the attesters’ approval made visible
`refunded`	EventFact	the escrow refund — absent while unobserved
`watermarks`	object	per chain domain, `{blockNumber, blockHash?, updatedAt}` — how far the observers have ingested (finalized head), on the chains the answer is dated against (Behavior): once a usable Open is observed, its output chains only; before that, every chain the deployment knows. Among those, absent chains have none published; omitted when no chain has one

EventFact is {chainDomain, txHash, blockNumber, observedAt}. observedAt is when the hub stored the observation, not the block time. No amounts are served here (the GET /orders legs carry them). The first observation of each event wins.

Behavior

The dating rule. An absent fact means “not observed (yet)”, never an error — with one guard: an absent filled is only returned if the hub can date it.

The hub finds the order’s destination chains from its observed Open (each output’s chain). With no usable Open, it uses every chain the deployment knows.
For each of those chains it needs a published observer watermark no older than infinity.chains.readMaxStalenessMs (default 30 000 ms).
If a destination chain cannot be resolved, or any watermark is missing or stale, the answer is refused with EIN0051 — which means “cannot tell”, never “not filled”.
When filled is present the watermarks are disclosure only.

The hub compares nothing with a deadline; the client’s withdraw rule is in Refunds.

Errors

Code	When
`EIN0051`	an absent fill that cannot be dated, or a store outage

This route never returns EIN0009. 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/onchain/0x8c7f293ae9851d2919e1543d0268483a0636bef9417240b0aa15258c508e32b9/fill \
  -H "x-api-key: $HUB_API_KEY"

Response

Illustrative values; formats follow the Response table.

{
  "success": true,
  "request_id": "96a7b8c9-d0e1-4c16-a172-839405162738",
  "data": {
    "onchainOrderId": "0x8c7f293ae9851d2919e1543d0268483a0636bef9417240b0aa15258c508e32b9",
    "open": { "chainDomain": "eip155-1", "txHash": "0x7e3a9c1b5d2f8e4a0c6b3d9f1e7a5c2b8d4f0a6e3c9b1d7f5a2e8c4b0f6d3a9e", "blockNumber": 7054, "observedAt": "2026-09-22T12:00:35Z" },
    "filled": { "chainDomain": "eip155-56", "txHash": "0x4b8d2f6a1e9c3b7d5f0a8e2c6b4d9f1a3e7c5b0d8f2a6e4c1b9d3f7a5e0c8b2d", "blockNumber": 7059, "observedAt": "2026-09-22T12:00:50Z" },
    "watermarks": {
      "eip155-56": { "blockNumber": 7061, "blockHash": "0x24b46941e1b961c61d47168c30d44f60560924e9709fac3a26cd3c2e2bc13b1b", "updatedAt": "2026-09-22T12:01:00Z" }
    }
  }
}

settled and refunded are absent: unobserved at this snapshot. watermarks holds only eip155-56, the Open’s output chain.

// client: your InteropClient (see /infinity-interop/sdk/installation)
const oc = await client.api.getOnchainFill(onchainOrderId);

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