> 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 are public capability-by-hash reads. They 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": { "...": "decoded unsigned transaction" },
  "refundPercent": 90,
  "refundRecipient": "0x..."
}
```

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 local 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.