---
title: "GET /v2/market/tokens/{chain_id}/{address}/trades"
method: GET
path: "/v2/market/tokens/{chain_id}/{address}/trades"
tags: ["Product Market"]
---

# GET /v2/market/tokens/{chain_id}/{address}/trades

`GET /v2/market/tokens/{chain_id}/{address}/trades`

## Request

- Base URL: `https://api.arbital.xyz` (the document declares no server; this is the origin it was published from)
- URL: `https://api.arbital.xyz/v2/market/tokens/{chain_id}/{address}/trades`
- Auth: none declared

Returns a newest-first, provider-normalized page of observed on-chain token trades with an opaque next_cursor. Default application/json remains the strict legacy representation. Send the exact Accept value application/vnd.arbital.trade-page+json to request optional evidence; other Accept values retain legacy JSON. Responses vary by Accept and are no-store. Older servers may return legacy JSON to this request; consumers must tolerate absent evidence without inventing it. Arc history uses Mobula. Values are display-only market data and are not settlement or execution authority.

## Path parameters

- `chain_id` 'solana:mainnet-beta' | 'eip155:1' | 'eip155:56' | 'eip155:143' | 'eip155:4663' | 'eip155:5042' | 'eip155:8453' | 'eip155:42161', required
- `address` string, required

## Query parameters

- `limit` integer
- `cursor` string
- `offset` integer

## Response `200`

Bounded on-chain token trade page

- ProductTokenTradePageV1
  - `asset` union, required
    - object
      - `address` string, required
      - `chain_id` 'solana:mainnet-beta', required
    - object
      - `address` string, required
      - `chain_id` 'eip155:1' | 'eip155:56' | 'eip155:143' | 'eip155:4663' | 'eip155:5042' | 'eip155:8453' | 'eip155:42161', required
  - `next_cursor` string, nullable, required: Opaque cursor for the next page. Clients must not parse or construct it.
  - `next_offset` integer, nullable, required
  - `observed_at_ms` string, required
  - `trades` ProductTokenTradeV1[], required
    - `asset` union, required
      - object
        - `address` string, required
        - `chain_id` 'solana:mainnet-beta', required
      - object
        - `address` string, required
        - `chain_id` 'eip155:1' | 'eip155:56' | 'eip155:143' | 'eip155:4663' | 'eip155:5042' | 'eip155:8453' | 'eip155:42161', required
    - `event_id` string, required
    - `fees` ProductTokenTradeFeesV1, required
      - `gas_usd` string, nullable, required
      - `mev_usd` string, nullable, required
      - `platform_usd` string, nullable, required
      - `total_usd` string, nullable, required
    - `market_cap_usd` string, nullable, required
    - `occurred_at_ms` string, required
    - `platform` ProductTokenTradePlatformV1, required
      - `id` string, nullable, required
      - `logo_url` string, uri, nullable, required
      - `name` string, nullable, required
    - `pool_address` string, required
    - `price_usd` string, required
    - `side` 'buy' | 'sell', required
    - `token_amount` string, required
    - `token_amount_atomic` string, nullable, required
    - `trader` ProductTokenTradeActorV1, required
      - `address` string, required
      - `entity_logo_url` string, uri, nullable, required
      - `entity_name` string, nullable, required
      - `is_developer` boolean, required
      - `labels` string[], required
    - `transaction_hash` string, required
    - `usd_amount` string, required

## Other responses

- `400`: Stable machine-readable problem. HTTP 429 and 503 responses include retry and cache-validity fields plus Retry-After and X-Request-ID headers.
- `404`: Stable machine-readable problem. HTTP 429 and 503 responses include retry and cache-validity fields plus Retry-After and X-Request-ID headers.
- `408`: Stable machine-readable problem. HTTP 429 and 503 responses include retry and cache-validity fields plus Retry-After and X-Request-ID headers.
- `413`: Stable machine-readable problem. HTTP 429 and 503 responses include retry and cache-validity fields plus Retry-After and X-Request-ID headers.
- `429`: Stable machine-readable problem. HTTP 429 and 503 responses include retry and cache-validity fields plus Retry-After and X-Request-ID headers.
- `503`: Stable machine-readable problem. HTTP 429 and 503 responses include retry and cache-validity fields plus Retry-After and X-Request-ID headers.

---

[API](https://skmtc.dev/arbital/apis/arbital-api.md) - [All operations](https://skmtc.dev/arbital/apis/arbital-api/llms.txt) - [OpenAPI document](https://skmtc.dev/arbital/apis/arbital-api/revisions/bb0185edf43a?raw)