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

# Get Transaction Status

Retrieve the status of a transaction by chain and transaction hash. Supports EVM, Solana, and Bitcoin.

**Endpoint:** `GET /api/v1/status/transaction/{txHash}`\
**Auth:** Required (`Authorization: Bearer YOUR_API_KEY`)

## Path parameters

| Parameter | Type   | Required | Description      |
| --------- | ------ | -------- | ---------------- |
| `txHash`  | string | Yes      | Transaction hash |

## Query parameters

| Parameter  | Type   | Required | Description                                 | Example       |
| ---------- | ------ | -------- | ------------------------------------------- | ------------- |
| `chainRef` | string | Yes      | Chain identifier. Required query parameter. | `eth-mainnet` |

## Example

{% tabs %}
{% tab title="cURL" %}

```bash
curl -X GET 'https://api.gateway.zert.com/api/v1/status/transaction/0x123...?chainRef=eth-mainnet' \
  -H 'Authorization: Bearer YOUR_API_KEY'
```

{% endtab %}

{% tab title="Example Response" %}

```json
{
  "data": {
    "txHash": "0x123...",
    "chain": "eth-mainnet",
    "status": "confirmed",
    "confirmedAtMs": 1745400000000
  },
  "meta": {
    "requestId": "req_xyz",
    "timestamp": "2026-04-23T12:00:00.000Z"
  }
}
```

{% endtab %}
{% endtabs %}

## Transaction status values

| Status      | Description                              |
| ----------- | ---------------------------------------- |
| `pending`   | Transaction submitted, not yet confirmed |
| `confirmed` | Transaction confirmed on chain           |
| `failed`    | Transaction failed                       |

## Responses

| Code | Description                               |
| ---- | ----------------------------------------- |
| 200  | Transaction status found                  |
| 400  | Missing or invalid `chainRef`             |
| 401  | Unauthorized (missing or invalid API key) |
| 404  | Transaction not found                     |
| 502  | Upstream error                            |

{% embed url="<https://api.gateway.zert.com/docs>" %}
Zert API — Transaction Status
{% endembed %}


---

# 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.zert.com/api-reference/status-and-tracking/get-transaction-status.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.