GET
/
api
/
{chainId}
/
token
/
{tokenId}
Get Token Details
curl --request GET \
  --url https://api.adamik.io/api/{chainId}/token/{tokenId} \
  --header 'Authorization: <api-key>'
{
  "token": {
    "type": "TRC10",
    "id": "<string>",
    "name": "<string>",
    "ticker": "<string>",
    "decimals": "<string>",
    "contractAddress": "<string>"
  }
}

Authorizations

​
Authorization
string
header
required

Path Parameters

​
chainId
enum<string>
required
Available options:
algorand,
cosmoshub,
cosmoshub-testnet,
osmosis,
osmosis-testnet,
celestia,
celestia-testnet,
dydx,
axelar,
ethereum,
sepolia,
holesky,
zksync,
zksync-sepolia,
injective-evm-testnet,
base,
base-sepolia,
optimism,
optimism-sepolia,
arbitrum,
arbitrum-sepolia,
polygon,
polygon-amoy,
bsc,
bsc-testnet,
linea,
linea-sepolia,
avalanche,
avalanche-fuji,
gnosis,
gnosis-chiado,
moonbeam,
moonriver,
moonbase,
fantom,
ton,
chiliz,
chiliz-testnet,
injective,
akash,
band,
dymension,
kyve,
terra2,
stargaze,
tron,
evmos,
irisnet,
juno,
lum-network,
omniflix,
sei,
medibloc,
passage,
quasar,
seda,
sommelier,
shentu,
stride,
chihuahua,
bitsong,
persistence,
comdex,
fetch-ai,
humans-ai,
ki,
likecoin,
provenance,
quicksilver,
saga,
kava,
starknet,
starknet-sepolia,
babylon,
babylon-testnet,
monad-testnet,
berachain,
berachain-artio,
cronos,
world-chain,
solana,
aptos,
aptos-testnet
​
tokenId
string
required

Token ID. Format depends on the chain, e.g. contract address for EVM chains.

Examples:

"0xdAC17F958D2ee523a2206206994597C13D831ec7"

Response

200 - application/json

Returns detailed data about the token on the specified blockchain.

The response is of type object.