Tokens API

Lifetime transfer count

How many transfers a token has had in total, over its whole lifetime -- one running number, not a bounded list of events. Solana and RHC.

GET/api/external/token-analysis/transfer-count/{chain}/{mint}

Chains

Send your key in the x-dex-data-key header. Replace each <placeholder> with a real value.

curl -H "x-dex-data-key: $DEXDATA_API_KEY" \
  "https://api.dexdata.io/api/external/token-analysis/transfer-count/SOL/<mint>"

Parameters
Parameter	Description
`chain` path · string · required	SOL and RHC; every other chain returns 400, because no wired source reports this there.
`mint` path · string · required	The token mint address (the token contract address on RHC).

A JSON response. Every field is always present; null means the value could not be established, never zero.

Response fields of Lifetime transfer count
Field	Type	Description
`transferCount`	number \| null	The token's lifetime transfer count (mints included; burns observed on RHC and inferred on SOL). `null` when the source has no reading — including when the source itself reads a literal `0`, which was measured to be indistinguishable from "this address is not a real token" rather than a genuine zero-transfer token (a real token's own mint event alone guarantees at least one).

Charged only when the call succeeds. Prices as of 2026-10-30; the current ones are always in the API reference.

Raw transfer events
The same event family's running LIFETIME total, not a bounded window of individual events.
A wallet's lifetime transfer count
The same count for a TOKEN rather than for a wallet.
DCA flow against one counter-token
Recurring (DCA) order flow between this token and ONE named counter-token, split by direction -- not the token's whole DCA picture.
A token's risk-score history over time
The history behind token-score: the same source's risk reading sampled over a trailing window (1d/7d hourly, 30d daily) instead of read once. ETH, BNB and BASE only.
A token's own submitted description and social links
A project's own curated description, verified badge, and extended social links (Discord, GitHub, whitepaper) beyond what identity already publishes.
Which wallets hold the token together, as clusters?
Groups of connected holder wallets, largest share first: each cluster's share of supply, its wallets, the wallets linking them and the venues used in one time window. Evidence, not proof.

Sign in, create a key and make your first call in a minute. Free credits every month, and you only pay for calls that succeed.