> ## 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.

# Polymarket Get Trade History

Get trade history for the authenticated user on Polymarket. Supports filtering by market, asset ID, and time range. Returns paginated trade records with cursor. Ideal for: trade analysis, P&L tracking, tax reporting, portfolio performance review.

![Polymarket Get Trade History logo](https://cdn.b3.fun/b3os-icons/polymarket-icon.png)
Catalog action Utility wallet

Get trade history for the authenticated user on Polymarket. Supports filtering by market, asset ID, and time range. Returns paginated trade records with cursor. Ideal for: trade analysis, P&L tracking, tax reporting, portfolio performance review.


## At a Glance

| Field | Value |
| --- | --- |
| Action ID | `polymarket-get-trade-history` |
| Category | Utility |
| Connector | `wallet` |
| Requires gas | No |
| Funds movement | None declared |
| Tags | `polymarket`, `trades`, `history`, `read` |

## Payload Schema

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `market` | `string` | No | Filter trades by market condition ID |
| `assetId` | `string` | No | Filter trades by asset/token ID |
| `before` | `string` | No | Filter trades before this timestamp \(ISO 8601\) |
| `after` | `string` | No | Filter trades after this timestamp \(ISO 8601\) |
| `cursor` | `string` | No | Pagination cursor from a previous response |

## Result Schema

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `trades` | `array` | Yes | Array of trade records |
| `count` | `number` | Yes | Total count of trades |
| `nextCursor` | `string` | No | Cursor for next page of results |

## Examples

**Workflow node**

```json
{
  "type": "polymarket-get-trade-history",
  "payload": {
    "market": "example-market",
    "assetId": "ETH",
    "before": "example-before",
    "after": "example-after",
    "cursor": "example-cursor"
  },
  "children": [],
  "connector": {
    "type": "wallet",
    "id": "conn_wallet"
  }
}
```
  **Test with API**

```bash
curl -X POST "https://api.b3os.org/v1/actions/polymarket-get-trade-history/test" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "inputs": {
    "market": "example-market",
    "assetId": "ETH",
    "before": "example-before",
    "after": "example-after",
    "cursor": "example-cursor"
  }
}'
```

**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.