Tracking and refunds

Tracking endpoints are public capability-by-hash reads. They never return signed raw transaction bytes or signatures.

Transaction status

curl https://orderflow.ethgas.com/v1/tx/0x<TRANSACTION_HASH>

{
  "status": "FORWARDED",
  "hash": "0x...",
  "timeReceived": "2026-09-07T12:00:00.000Z",
  "transaction": { "...": "decoded unsigned transaction" },
  "refundPercent": 90,
  "refundRecipient": "0x..."
}

An unknown hash still returns HTTP 200, with status: "UNKNOWN" and null detail fields.

Bundle status

curl "https://orderflow.ethgas.com/v1/bundle?hash=0x<BUNDLE_HASH>"

{
  "status": "FORWARDED",
  "bundleHash": "0x...",
  "builderBundleHash": "0x...",
  "blockNumber": "0x12abcde",
  "timeReceived": "2026-09-07T12:00:00.000Z"
}

bundleHash is the engine's identity. builderBundleHash is null until an accepting builder returns a valid bundle hash.

Partner refunds

Partner originators can list only their own refund liabilities and confirmed payouts:

curl https://orderflow.ethgas.com/v1/<API_KEY>/refunds

The response groups confirmed entries by payout transaction and pending batch entries by recipient. Refund amounts are decimal wei strings.

Refund reporting follows finalized chain data with a fixed 32-block lag. A forwarded bundle does not by itself guarantee a refund: the engine must attribute an eligible finalized builder payment to the originator flow.