---
title: "List Transactions"
method: GET
path: "/v1/transactions"
tags: ["Wallets"]
---

# List Transactions

`GET /v1/transactions`

Retrieves a paginated list of transactions associated with the authenticated client. Results are sorted by creation date in descending order (most recent first). Supports filtering by wallet address and pagination controls.

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

## Query parameters

- `from` string — Filter transactions by sender wallet address or ENS name.
- `limit` integer — Number of transactions to return per page (1-100).
- `page` integer — Page number for pagination, starting from 1.

## Response `200`

Transactions retrieved successfully. Returns a paginated list of transactions with metadata including creation and confirmation timestamps.

- object
  - `result` object, required
    - `pagination` object, required
      - `hasMore` boolean — Whether there are more items available
      - `limit` number, nullable — Number of items per page
      - `page` number, nullable — Current page number
      - `totalCount` number, nullable — Total number of items available
    - `transactions` 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 pagination parameters are out of range or wallet address format is invalid.
- `401` — Authentication required. The request must include a valid `x-client-id` header for frontend usage or `x-secret-key` for backend usage.
- `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)