> ## 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 Trades Summary

Get aggregate closed-trade statistics for a Hyperliquid wallet from HyperTracker. Shows win/loss record, win rate, average trade duration, and long/short breakdown. Ideal for: trader analysis, wallet evaluation, performance assessment.

Catalog action Blockchain Data

Get aggregate closed-trade statistics for a Hyperliquid wallet from HyperTracker. Shows win/loss record, win rate, average trade duration, and long/short breakdown. Ideal for: trader analysis, wallet evaluation, performance assessment.


## At a Glance

| Field | Value |
| --- | --- |
| Action ID | `hypertracker-get-wallet-trades-summary` |
| Category | Blockchain Data |
| Connector | Not required |
| Requires gas | No |
| Funds movement | None declared |
| Tags | `hypertracker`, `hyperliquid`, `wallet`, `trades`, `analytics`, `read` |

## Payload Schema

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `apiKey` | `string` | No | HyperTracker API key \(falls back to HYPERTRACKER_API_KEY env var\) |
| `address` | `string` | Yes | Wallet address to query \(0x-prefixed EVM address\). |

## Result Schema

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `address` | `string` | Yes | Wallet address queried |
| `totalTrades` | `number` | Yes | Total number of closed trades |
| `wins` | `number` | Yes | Number of winning trades |
| `losses` | `number` | Yes | Number of losing trades |
| `winRate` | `number` | Yes | Win rate as a percentage \(0-100\) |
| `avgDuration` | `number` | Yes | Average trade duration in milliseconds |
| `avgDurationHuman` | `string` | Yes | Average trade duration in human-readable format \(e.g., '2h 15m'\) |
| `longTrades` | `number` | Yes | Number of long trades |
| `shortTrades` | `number` | Yes | Number of short trades |
| `longPercent` | `number` | Yes | Percentage of trades that were long \(0-100\) |
| `updatedAt` | `string \| null` | Yes | ISO 8601 timestamp of last data update, or null if unavailable |

## Examples

**Workflow node**

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

```bash
curl -X POST "https://api.b3os.org/v1/actions/hypertracker-get-wallet-trades-summary/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.