Skip to main content
GET
Get Comprehensive Token Details
Batch Support Available: This endpoint supports batch queries via POST method for fetching multiple tokens in a single request. Jump to Batch Query section

Overview

The Token Details endpoint provides comprehensive token data including metadata, liquidity, volume, price changes, holdings, and trading activity over multiple timeframes. It supports both single-item queries (GET) and batch queries (POST) for efficient data retrieval by token address.

GET Method - Single Item Query

Retrieve detailed token information for a single token.

Query Parameters

  • blockchain (required) — The blockchain identifier (e.g., evm:1, solana, ethereum)
  • address (required) — Direct token address
  • currencies (optional) — Comma-separated list of fiat currencies for price conversion. Defaults to USD. Supported currencies: USD, EUR, GBP, JPY, CHF, CAD, AUD, CNY, KRW, INR, BRL

Step-by-Step Tutorial and Video Walkthrough

  • Check out the guide: Here

Usage Examples

Response Format

POST Method - Batch Query

Retrieve token details for multiple tokens in a single request for improved efficiency.

Request Body

Body Parameters

The request body is an array of query objects, where each object contains:
  • blockchain (required) — Blockchain id or name
  • address (required) — Direct token address
  • currencies (optional) — Comma-separated list of fiat currencies for price conversion. Defaults to USD

Usage Examples

Response Format

Multi-Currency Support

When you specify multiple currencies using the currencies parameter, the response will include additional fields for each currency. For every field ending in USD, a corresponding field will be added for each requested currency.

Example with currencies=EUR,USD

Converted Fields

The following field patterns are automatically converted:
  • priceUSDprice{CURRENCY}
  • marketCapUSD, marketCapDilutedUSDmarketCap{CURRENCY}, marketCapDiluted{CURRENCY}
  • volume*USD (all timeframes) → volume*{CURRENCY}
  • volumeBuy*USD, volumeSell*USDvolumeBuy*{CURRENCY}, volumeSell*{CURRENCY}
  • liquidityUSD, liquidityMaxUSDliquidity{CURRENCY}, liquidityMax{CURRENCY}
  • approximateReserveUSDapproximateReserve{CURRENCY}
  • athUSD, atlUSDath{CURRENCY}, atl{CURRENCY}
  • feesPaid*USD, totalFeesPaidUSDfeesPaid*{CURRENCY}, totalFeesPaid{CURRENCY}
  • organicVolume*USDorganicVolume*{CURRENCY}
Exchange rates are fetched from reliable forex data providers and cached for optimal performance. Rates are updated every 30 minutes.

Response Field Definitions

Security Object

All fields in the security object are optional — they are only present when the relevant data is available for the token. A field being absent means the check was not performed or no data is available (not that the token is safe).
EVM vs Solana availability: Most fields apply to EVM chains. noMintAuthority is Solana-specific. isHoneypot, isNotOpenSource, renounced, locked, isWhitelisted, isMintable, modifyableTax, and selfDestruct are EVM-only.

PumpFun Flags

These fields are specific to tokens launched on PumpFun (Solana). They are null for non-PumpFun tokens.

OG Coin

Liquidity Burn

Holdings Data

The response includes various holdings percentage fields that help identify token distribution patterns:
  • top10HoldingsPercentage, top50HoldingsPercentage, top100HoldingsPercentage, top200HoldingsPercentage — Percentage of total supply held by the top N holders
  • devHoldingsPercentage — Percentage held by the token deployer/developer
  • insidersHoldingsPercentage — Percentage held by wallets identified as insiders (early participants with privileged access)
  • bundlersHoldingsPercentage — Percentage held by wallets using bundling strategies (multiple transactions in a single block)
  • snipersHoldingsPercentage — Percentage held by wallets that sniped the token at launch
  • proTradersHoldingsPercentage — Percentage held by accounts that interact with trading terminals (e.g., BullX, Photon, GMGN, Trojan, and other trading bots/interfaces). These wallets are identified by their interaction patterns with known trading terminal contracts and interfaces.
  • freshTradersHoldingsPercentage — Percentage held by newly funded wallets (within last 24 hours)
  • insidersCount, bundlersCount, snipersCount, freshTradersCount, proTradersCount — Number of holders in each category

Fees Paid Data

The feesPaid* fields represent an aggregation of transaction costs across all trades for this token:
  • feesPaid1minUSD, feesPaid5minUSD, feesPaid15minUSD, feesPaid1hUSD, etc. — Total fees paid over the specified timeframe
  • totalFeesPaidUSD — Cumulative fees paid since token creation
What’s included:
  • Priority fees (Solana) / Gas fees (EVM chains)
  • UI fees charged by trading terminals and interfaces
  • Protocol fees from DEX platforms
These values are approximate estimates based on heuristics. The calculation does not account for cashback systems, fee rebates, or certain terminal-specific fee structures. Use these values as directional indicators rather than precise figures.

Organic Metrics

The organic* fields filter out wash trading and bot activity to provide cleaner trading metrics:
  • organicTrades* — Trade count excluding suspected bot/wash activity
  • organicTraders* — Unique trader count excluding suspected bots
  • organicVolume* — Volume excluding suspected artificial activity
  • organicBuys*, organicSells* — Buy/sell counts excluding bots
  • organicBuyers*, organicSellers* — Unique buyer/seller counts excluding bots

Use Cases

  • GET: Single token monitoring, real-time price checks, detailed token analysis
  • POST: Portfolio analysis, bulk token research, multi-token dashboard data

Query Parameters

chainId
string

Blockchain chain ID (e.g., "evm:56", "solana:solana")

address
string

Token contract address

currencies
string

Comma-separated list of currencies for price conversion

Response

200 - application/json

Token Holder response

data
object
required
hostname
string