Skip to main content
GET
Token trades
Newest first. Page back with the next of the previous page as cursor; next is null on the last page. wallet= keeps one wallet’s trades (on EVM chains, as wallet trades gives them: one row per pool, with pool). from and to (Unix ms) walk a time window: the first page starts just below to, the page that reaches from has next: null, and next carries the window. For oldest first, walk the window and reverse it:
  • A row is one wallet’s side of a swap. One transaction can give several rows, also for one wallet: on Solana two wallets that sign it are two rows; a multi-hop swap through the token can be a sell and a buy of the same wallet, and a swap routed through several pools several rows on the same side; on EVM chains a row is one swap log.
  • Key rows on id: the same on REST pages, the trades channel’s snapshot, frames and retracts. The pages of one walk do not repeat a row. Never key on signature alone, or signature + wallet.
  • side is the side of the token: buy means the wallet received it.
  • quoteAmount, quoteSymbol and quoteToken are the other side of the swap, in its own units: quoteSymbol names the chain’s coin for its wrapped token (SOL, ETH, BNB), else the quote’s symbol (USDC, USD1, …).
  • volumeNative and priceNative are the trade in the chain’s coin (SOL, ETH, BNB).
  • wallet is null when no source names the trader; on EVM chains a pool or the V4 PoolManager is never given as one.
  • pool and dex can be null when the source does not say which pool. volumeUsd, priceUsd, quoteAmount and quoteSymbol can be null on a history row too.
  • On EVM chains, while a token is watched, the first page also carries live legs history lacks: it can hold up to twice limit rows.
  • The row count does not end the walk: a page can hold fewer rows than limit, even none, and still carry next. A Solana page may also hold more than limit rows, when one transaction alone has more, and the first page may leave out the last half second of trades, which the live channel carries.
  • A Solana page may answer 503 with Retry-After: it cannot be served right now. Ask again after it, with the same cursor.
Live: the trades channel sends the last 100 trades, then every new one.

Authorizations

x-api-key
string
header
required

Path Parameters

chain
string
required

sol, eth, bsc, base or robinhood (or an alias or network id)

Example:

"sol"

address
string
required

Token address (mint or contract)

Example:

"DezXAZ8z7PnrnRJjz3wXBoRgixCa6xjnB7YaB1pPB263"

Query Parameters

limit
integer
default:50

Rows per page; a Solana page may hold more when one transaction alone has more

Required range: x <= 200
cursor
string

The next of the previous page, as given (URL-encoded). Opaque, and its format may change: never build or alter one. One the server can no longer honour is a 400: start again from the first page. A cursor that keeps failing (a 400, or a 503 again and again) while the first page loads: start again from the first page too.

wallet
string

Only this wallet's trades (on Solana, a 32-byte key)

from
integer

The oldest trade time to include, Unix ms (inclusive). Whole milliseconds, at least 1e12 (seconds are a 400)

to
integer

The newest trade time, Unix ms (exclusive): the first page starts just below it. Ignored with cursor

Response

A page of trades

data
object[]
next
string | null