> ## Documentation Index
> Fetch the complete documentation index at: https://docs.b3os.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Get Wallet Transactions (Zerion)

Retrieve transaction history for any wallet address via Zerion API. Returns detailed transaction data including operation type, transfers, fees, and status. Supports filtering by operation type, chain, date range, and full-text search. Cursor-based pagination (max 100/page). Ideal for: transaction history display, wallet activity monitoring, trade tracking, fee analysis.

![Get Wallet Transactions (Zerion) logo](https://ai-icon.b3.fun/logo/zerion)
Catalog action Blockchain Data

Retrieve transaction history for any wallet address via Zerion API. Returns detailed transaction data including operation type, transfers, fees, and status. Supports filtering by operation type, chain, date range, and full-text search. Cursor-based pagination (max 100/page). Ideal for: transaction history display, wallet activity monitoring, trade tracking, fee analysis.


## At a Glance

| Field | Value |
| --- | --- |
| Action ID | `zerion-get-wallet-transactions` |
| Category | Blockchain Data |
| Connector | Not required |
| Requires gas | No |
| Funds movement | None declared |
| Tags | `zerion`, `blockchain`, `wallet`, `transactions`, `activity`, `history`, `read` |

## Payload Schema

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `address` | `string` | Yes | The wallet address to query transactions for. |
| `cursor` | `string` | No | Pagination cursor from previous response \(nextCursor field\) |
| `pageSize` | `number` | No | Number of results per page. Range: 1-100. Default: 100 |
| `searchQuery` | `string` | No | Full-text search query \(2-64 characters\) |
| `operationTypes` | `array` | No | Filter by operation types: approve, burn, claim, delegate, deploy, deposit, execute, mint, receive, revoke, send, trade, withdraw |
| `chainIds` | `array` | No | Filter by chains. Accepts numeric EVM chain IDs \(e.g. 1, 56, 8453\) or Zerion slugs \(e.g. 'ethereum', 'polygon'\). Chains B3 supports but Zerion does not are rejected with INVALID_INPUT. |
| `trash` | `string` | No | Spam filter. Defaults to 'only_non_trash' \(spam/dust transactions excluded\) — pass 'no_filter' to include everything. |
| `minMinedAt` | `number` | No | Only transactions after this timestamp \(milliseconds\) |
| `maxMinedAt` | `number` | No | Only transactions before this timestamp \(milliseconds\) |
| `currency` | `string` | No | Currency to denominate values in. Default: usd |

## Result Schema

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `address` | `string` | Yes | - |
| `transactions` | `array` | Yes | - |
| `nextCursor` | `string` | No | Cursor for next page |

## Examples

**Workflow node**

```json
{
  "type": "zerion-get-wallet-transactions",
  "payload": {
    "address": "0x0000000000000000000000000000000000000000"
  },
  "children": []
}
```
  **Test with API**

```bash
curl -X POST "https://api.b3os.org/v1/actions/zerion-get-wallet-transactions/test" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "inputs": {
    "address": "0x0000000000000000000000000000000000000000"
  }
}'
```

**Use expressions for dynamic values**

Payload fields can use workflow expressions such as `{{$trigger.body.amount}}`, `{{$nodes.fetch.result.price}}`, and `{{$props.asset}}` when the value should come from a trigger, prior node, or reusable workflow prop.