> For the complete documentation index, see [llms.txt](https://docs.ethgas.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ethgas.com/orderflow/tracking-and-refunds.md).

# Tracking and refunds

Tracking endpoints provide status reads by hash. Responses never return signed raw transaction bytes or signatures.

## Transaction status

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

```json
{
  "status": "FORWARDED",
  "hash": "0x...",
  "timeReceived": "2026-09-07T12:00:00.000Z",
  "transaction": null,
  "refundPercent": null,
  "refundRecipient": null
}
```

Public transaction tracking returns the status, hash, and receipt time. The `transaction`, `refundPercent`, and `refundRecipient` fields are null.

To retrieve the decoded unsigned transaction and refund policy for an owned flow, use `https://orderflow.ethgas.com/v1/{API_KEY}/tx/{txHash}` with the owning partner originator's API key.

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

## Bundle status

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

```json
{
  "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:

```bash
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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ethgas.com/orderflow/tracking-and-refunds.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.