- Token metadata (symbol, name, decimals)
- Current USD pricing information
- Supply information
- Logo URLs when available
?chain_ids query parameter is mandatory.
To learn more about this query parameter, see the Supported Chains page.Native vs. ERC20 tokens
Theaddress path parameter can be set to native for chain-native assets or to an ERC20 contract address. Include the required ?chain_ids query parameter to select the chain. The response shape differs slightly for native assets vs ERC20 tokens.
Native asset
Use native as the address path parameter.
address path parameter. Additional fields like pool_size, total_supply, and fully_diluted_value may be present.
Token Prices
Sim looks up prices onchain. We use the most liquid onchain pair to determine a usd price. We return the available liquidity inpool_size as part of the response.
Historical prices
You can request historical point-in-time prices by adding the optionalhistorical_prices query parameter. Use whole numbers to specify the number of hours in the past. You can request up to three offsets. For example, historical_prices=8760 returns the price 8760 hours (approximately 1 year) ago. historical_prices=720,168,24 returns prices 720 hours (1 month) ago, 168 hours (1 week) ago, and 24 hours ago.
historical_prices query parameter is currently supported only on the EVM Token Info and EVM Balances endpoints.historical_prices array with one entry per offset:
price_usd and the values in historical_prices[].price_usd.
Pagination
This endpoint uses cursor-based pagination. You can use thelimit parameter to define the maximum page size.
Results might at times be less than the maximum page size.
The next_offset value is included in the initial response and can be utilized to fetch the next page of results by passing it as the offset query parameter in the next request.
next_offset to set the offset parameter of the next page of results. Using your own offset value will not have any effect.Compute Unit Cost
The Token Info endpoint has a fixed CU cost of 2 per request. Thechain_ids query parameter is required but does not change the CU cost. See the Compute Units page for detailed information.Headers
Used for authenticating requests. Provide an API key with a purpose of Sim API. See Authentication.
Path Parameters
The contract address of the token or 'native' for the native token of the chain
Query Parameters
Specify exactly one chain. Accepts a single numeric chain ID (e.g. ?chain_ids=1). Chain names are not accepted. See the Supported Chains Tags section.
Request historical point-in-time prices. Accepts integer | integer[]. Provide whole numbers representing hours in the past, with a maximum of 3 time offsets (e.g. 8760 for 1 year ago or 720,168,24 for 1 month, 1 week, and 1 day ago). When present, each token includes a historical_prices array with one entry per offset.
x >= 1This endpoint returns up to the number of supported chains. See Supported Chains to learn more.
x >= 0The offset to paginate through result sets; this is a cursor being passed from the previous response, only use what the backend returns here