Resolve fill by transaction

GET /v1/onchain/tx/{chainDomain}/{txHash}/order Resolve a transaction hash — typically the fillTransaction from GET /order/{orderId}/status — into the order’s observed lifecycle.

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

Not scoped to your organization. See Get on-chain fill for the id-format note.

Request

Path parameters

Param	Rules	Meaning
`chainDomain`	not validated	the canonical domain of the chain the transaction is on (e.g. `eip155-56`); an unknown or miscased domain finds nothing and then has no watermark, so it answers `EIN0051`
`txHash`	lowercased by the hub except on Solana and Sui (case-sensitive base58, used as given)	an EVM hash must include `0x`

Response

data: OnchainFill, as GET /onchain/{orderId}/fill.

Behavior

The hub looks for any tracked settler event (Open, Filled, Settled, Refunded) at the first nine event positions (0–8) of that transaction on that chain: its receipt’s logs on EVM chains, where every log counts, settler or not; its instructions on Solana, inner ones included. An event further in is not found.
A Solana Open signature does not resolve, while the same order’s settle signature does. Follow a Solana-origin order by onchainOrderId on GET /onchain/{orderId}/fill (known issue).
Hit: the answer is the full GET /onchain/{orderId}/fill view of that order, with its dating rule.
Miss: onchainOrderId is "" (present, empty) with no facts, and watermarks holds the named chain — “not observed yet, as of this position”, poll again. If that chain has no fresh watermark the miss is refused with EIN0051.

Errors

Code	When
`EIN0051`	see behaviour above

Never send an empty segment: the path is then not a route. 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/tx/eip155-56/0x4b8d2f6a1e9c3b7d5f0a8e2c6b4d9f1a3e7c5b0d8f2a6e4c1b9d3f7a5e0c8b2d/order \
  -H "x-api-key: $HUB_API_KEY"

Response

Illustrative values; formats follow the Response table. This is the hit case — the same object GET /onchain/{orderId}/fill returns for this order’s on-chain id. A miss returns the same shape with no facts:

{"onchainOrderId": "", "watermarks": {"eip155-56": {"blockNumber": 7061, "blockHash": "0x24b46941e1b961c61d47168c30d44f60560924e9709fac3a26cd3c2e2bc13b1b", "updatedAt": "2026-09-22T12:01:00Z"}}}

{
  "success": true,
  "request_id": "a7b8c9d0-e1f2-4d27-b283-940516273849",
  "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" }
    }
  }
}

// client: your InteropClient (see /infinity-interop/sdk/installation)
const oc = await client.findOrderByTx("eip155-56", st.fillTransaction!.hash!);

Get started

Core concepts

Resources

API reference

SDK

SDK reference

Resolve fill by transaction

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