GET /v1/onchain/{orderId}/order
The escrow’s raw order tuple — what refund(order) needs from a device that holds only the
on-chain id.
Not scoped to your organization. See Get on-chain fill for the
id-format note.
Request
Path parameters
Response
data (OnchainOrder):
Behavior
- The settler honours a refund only for a tuple that hashes to the order id, and a refund pays only the order’s own user — so the blob needs availability, not confidentiality.
- EVM origins only. Non-EVM order bodies are not served: such an order answers
EIN0009permanently, even once its Open, fill and settle are observed (known issue). A Solana-origin order refunds through Get Solana refund instead.
Errors
Never send an empty id:
/onchain//order is 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
Response
Illustrative values; formats follow the Response table.rawOrder is elided here: a real ABI-encoded StandardOrder is not derivable from the documented sources.
See also
- SDK:
client.api.getOnchainOrder();client.prepareEvmRefund()andclient.refundEvmOrder()build and check the refund from it (Refunds) - Get Solana refund: the Solana counterpart
- Refunds
- Order lifecycle