---
title: "Get Transaction"
method: GET
path: "/v1/transactions/{transactionId}"
tags: ["Wallets"]
---

# Get Transaction

`GET /v1/transactions/{transactionId}`

Retrieves detailed information about a specific transaction using its unique identifier. Returns comprehensive transaction data including execution status, blockchain details, and any associated metadata.

**Authentication**: Pass `x-client-id` header for frontend usage from allowlisted origins or `x-secret-key` for backend usage.

## Path parameters

- `transactionId` string, required — Unique identifier of the transaction to retrieve.

## Response `200`

Transaction details retrieved successfully. Returns comprehensive transaction information including status, blockchain details, and execution metadata.

- object
  - `result` object, required
    - `batchIndex` integer, required — Index within transaction batch
    - `cancelledAt` string, nullable, required — ISO timestamp when transaction was cancelled, if applicable
    - `chainId` string, required — Blockchain network identifier as string
    - `clientId` string, required — Client identifier that initiated the transaction
    - `confirmedAt` string, nullable, required — ISO timestamp when transaction was confirmed on-chain
    - `confirmedAtBlockNumber` string, nullable, required — Block number where transaction was confirmed
    - `createdAt` string, required — ISO timestamp when transaction was created
    - `enrichedData` unknown
    - `errorMessage` string, nullable, required — Error message if transaction failed
    - `executionParams` unknown
    - `executionResult` unknown
    - `from` string, nullable, required — Sender wallet address
    - `id` string, required — Unique transaction identifier
    - `transactionHash` string, nullable, required — On-chain transaction hash once confirmed
    - `transactionParams` unknown
    - `status` 'QUEUED' | 'SUBMITTED' | 'CONFIRMED' | 'FAILED', nullable, required — Transaction status

## Other responses

- `400` — Invalid request parameters. This occurs when the transaction ID format is invalid or malformed.
- `401` — Authentication required. The request must include a valid `x-client-id` header for frontend usage or `x-secret-key` for backend usage.
- `404` — Transaction not found. The specified transaction ID does not exist or is not associated with the authenticated client.
- `500` — Internal server error. This may occur due to engine connectivity issues, database unavailability, or unexpected server errors.

---

[API](https://skmtc.net/thirdweb/apis/thirdweb-api.md) · [All operations](https://skmtc.net/thirdweb/apis/thirdweb-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/thirdweb/thirdweb-api/revisions/fb4cb67da1c7/schema)