Get Token Details
Path Parameters
string
required
The network the token lives on (e.g.
ethereum, solana, bsc). Retrieve valid network IDs from GET /networks.string
required
The token’s contract address. For EVM networks this is a checksummed hex address; for Solana it is a Base58 mint address.
Code Examples
Response Fields
string
required
The token’s contract address, matching the
address path parameter.string
required
Full token name as registered on-chain (e.g.
Wrapped Ether).string
required
Token ticker symbol (e.g.
WETH, USDC).string
required
Network ID where this token is deployed (e.g.
ethereum).integer
required
Number of decimal places used by the token contract. Use this to convert raw on-chain amounts to human-readable values.
string
required
Total token supply as a decimal string, adjusted for
decimals.string
required
Current token price in USD, derived from the deepest liquidity pool. Returned as a string to preserve precision for low-cap tokens.
string
required
Fully diluted valuation in USD (
price_usd × total_supply), returned as a decimal string.string
required
Total USD liquidity aggregated across all indexed pools for this token.
integer
required
Number of liquidity pools that include this token across all indexed DEXes on this network.
object
required
Rolling 24-hour trading statistics.
boolean
required
true if DexUtils has a logo image on file for this token.boolean
required
true if the token has been manually verified by the DexUtils team. Verified tokens have confirmed metadata and are less likely to be honeypots or impostors.Example Response
Example Response
Batch Token Lookup
The batch endpoint accepts a maximum of 100 tokens per request. If you need data for more tokens, split your list into chunks of 100 and send multiple requests.
Request Body
array
required
An array of token identifier objects. Each object must include both
network and address.Code Examples
Response
The batch endpoint returns a flat JSON array. Each element follows the same schema as the single-token response above — including the nested24h object. Elements appear in the same order as the input tokens array.