Get Token Info
Retrieve comprehensive real-time information about any ERC-20 token via Sim Dune API. Returns name, symbol, decimals, total supply, current price, 24h change, market cap, volume, liquidity, holder count, and logo. Supports multi-chain queries to find token deployments. Ideal for: token detail displays, pre-swap validation, price calculations, transaction data enrichment.
Catalog action Blockchain Data
Retrieve comprehensive real-time information about any ERC-20 token via Sim Dune API. Returns name, symbol, decimals, total supply, current price, 24h change, market cap, volume, liquidity, holder count, and logo. Supports multi-chain queries to find token deployments. Ideal for: token detail displays, pre-swap validation, price calculations, transaction data enrichment.
At a Glance
| Field | Value |
|---|---|
| Action ID | sim-dune-get-token-info |
| Category | Blockchain Data |
| Connector | Not required |
| Requires gas | No |
| Funds movement | None declared |
| Tags | sim-dune, blockchain, token, metadata, price, market-cap, volume, liquidity, erc20, info, details, read |
Payload Schema
| Field | Type | Required | Description |
|---|---|---|---|
tokenAddress | string | Yes | Token contract address or 'native' for native chain assets |
chainIds | array | No | Chain IDs to query (optional, defaults to all chains where token exists) |
historicalPrices | array | No | Historical price offsets in hours (max 3). E.g., [24, 168, 720] for 1 day, 1 week, 1 month ago |
limit | number | No | Maximum number of results per page |
offset | string | No | Pagination cursor from previous response (use nextOffset value) |
Result Schema
| Field | Type | Required | Description |
|---|---|---|---|
contractAddress | string | Yes | The queried contract address or 'native' |
tokens | array | Yes | Token information per chain |
warnings | array | No | Non-fatal processing issues |
nextOffset | string | No | Pagination cursor for next page |
Examples
json{ "type": "sim-dune-get-token-info", "payload": { "tokenAddress": "0x0000000000000000000000000000000000000000" }, "children": []}
bashcurl -X POST "https://api.b3os.org/v1/actions/sim-dune-get-token-info/test" \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "inputs": { "tokenAddress": "0x0000000000000000000000000000000000000000" }}'
Payload fields can use workflow expressions such as {{$trigger.body.amount}}, {{$nodes.fetch.result.price}}, and {{$props.asset}} when the value should come from a trigger, prior node, or reusable workflow prop.