---
title: "Get \"Token God Mode\" (TGM) who bought/sold data"
method: POST
path: "/api/v1/tgm/who-bought-sold"
tags: ["Token God Mode"]
---

# Get "Token God Mode" (TGM) who bought/sold data

`POST /api/v1/tgm/who-bought-sold`

This endpoint provides an aggregated summary of trade volumes in USD for addresses. It can be used to identify addresses that are net buyers or sellers of a token within a time period.

## Request body

- TGMWhoBoughtSoldRequest — Request model for TGM who bought/sold endpoint. This endpoint provides an aggregated summary of trade volumes in USD for addresses involved in DEX (Decentralized Exchange) trades for a specific token.
  - `chain` 'arbitrum' | 'avalanche' | 'base' | 'bnb' | 'ethereum' | 'hyperevm' | 'hyperliquid' | 'injective' | 'iotaevm' | 'linea' | 'mantle' | 'mantra' | 'monad' | 'near' | 'optimism' | 'plasma' | 'polygon' | 'robinhood' | 'sei' | 'solana' | 'sonic' | 'starknet' | 'sui' | 'ton' | 'tron', required — Chains supported in TGM (Token God Mode) endpoints.
  - `token_address` string, required — Address of token
  - `buy_or_sell` 'BUY' | 'SELL' — TGM who bought/sold type.
  - `date` DateRange, required — Date range model matching the API schema.
    - `from` string — Start date in ISO 8601 format (e.g., 2025-01-01T00:00:00Z or 2025-01-01)
    - `to` string — End date in ISO 8601 format (e.g., 2025-01-31T23:59:59Z or 2025-01-31)
  - `pagination` PaginationRequest — Pagination parameters for API requests.
    - `page` integer — Page number (1-based)
    - `per_page` integer — Number of records per page (max 1000)
  - `filters` TGMWhoBoughtSoldFilters — Filters for TGM who bought/sold endpoint. These filters control which traders and trade data are included.
    - `include_smart_money_labels` LabelType[] — Include smart money labels for traders
    - `exclude_smart_money_labels` LabelType[] — Exclude smart money labels for traders
    - `address` union — Trader address filter
      - string
      - string[]
    - `address_label` union — Trader label filter
      - string
      - string[]
    - `bought_token_volume` NumericRangeFilter — Filter for numeric values (floats) with optional min/max bounds. Use for prices, volumes, ratios, and other decimal values. - Values between -10.5 and 100.75
      - `min` number — Minimum value (inclusive)
      - `max` number — Maximum value (inclusive)
    - `sold_token_volume` NumericRangeFilter — Filter for numeric values (floats) with optional min/max bounds. Use for prices, volumes, ratios, and other decimal values. - Values between -10.5 and 100.75
      - `min` number — Minimum value (inclusive)
      - `max` number — Maximum value (inclusive)
    - `token_trade_volume` NumericRangeFilter — Filter for numeric values (floats) with optional min/max bounds. Use for prices, volumes, ratios, and other decimal values. - Values between -10.5 and 100.75
      - `min` number — Minimum value (inclusive)
      - `max` number — Maximum value (inclusive)
    - `bought_volume_usd` NumericRangeFilter — Filter for numeric values (floats) with optional min/max bounds. Use for prices, volumes, ratios, and other decimal values. - Values between -10.5 and 100.75
      - `min` number — Minimum value (inclusive)
      - `max` number — Maximum value (inclusive)
    - `sold_volume_usd` NumericRangeFilter — Filter for numeric values (floats) with optional min/max bounds. Use for prices, volumes, ratios, and other decimal values. - Values between -10.5 and 100.75
      - `min` number — Minimum value (inclusive)
      - `max` number — Maximum value (inclusive)
    - `trade_volume_usd` NumericRangeFilter — Filter for numeric values (floats) with optional min/max bounds. Use for prices, volumes, ratios, and other decimal values. - Values between -10.5 and 100.75
      - `min` number — Minimum value (inclusive)
      - `max` number — Maximum value (inclusive)
  - `order_by` SortOrderTGMWhoBoughtSoldSortField[] — Custom sort order to override the endpoint's default ordering. Examples: - [{"field": "bought_volume_usd", "direction": "DESC"}] - Sort by bought volume descending - [{"field": "sold_volume_usd", "direction": "ASC"}] - Sort by sold volume ascending
    - `field` 'bought_volume_usd' | 'sold_volume_usd' | 'token_trade_volume' | 'trade_volume_usd' | 'bought_token_volume' | 'sold_token_volume', required — Sortable fields for TGM who-bought-sold endpoint.
    - `direction` 'ASC' | 'DESC', required — Enum for sort directions.

## Response `200`

TGM who bought/sold data

- TGMWhoBoughtSoldResponse — Response model for TGM who bought/sold endpoint. Contains a list of address records with pagination and metadata.
  - `data` TGMWhoBoughtSold[], required — List of TGM who bought/sold records
    - `address` string, required — The address that did the trades
    - `address_label` string — Label associated with the address
    - `bought_token_volume` number — The aggregate bought token volume for the address
    - `sold_token_volume` number — The aggregate sold token volume for the address
    - `token_trade_volume` number — The net token trade volume for the address
    - `bought_volume_usd` number — The aggregate bought volume in USD for the address
    - `sold_volume_usd` number — The aggregate sold volume in USD for the address
    - `trade_volume_usd` number — The net trade volume in USD for the address
  - `pagination` PaginationInfo, required — Pagination information for API responses.
    - `page` integer — Current page number
    - `per_page` integer — Number of records per page
    - `is_last_page` boolean — Whether this is the last page

## Other responses

- `400` — Bad Request - Invalid request parameters or malformed request
- `401` — Authentication error - No API key found in request
- `402` — Payment Required - This endpoint supports pay-per-request via x402 and MPP. x402 responses advertise payment options in `Payment-Required`; MPP responses advertise a fresh `WWW-Authenticate: Payment ...` challenge. Successful MPP responses may include `Payment-Receipt`.
- `403` — Forbidden - User does not have required subscription tier or has exceeded credit limit
- `404` — Not Found - The requested resource was not found
- `422` — Validation error - Invalid request parameters
- `429` — Too Many Requests - Rate limit exceeded
- `500` — Internal Server Error - An unexpected error occurred

---

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