How to Fetch STON.fi Token Metadata via REST API and TypeScript Client
STON.fi gives builders a clean HTTP API and TypeScript client so you can pull token names, symbols, decimals, images, prices and tags without decoding jetton cells yourself.
🔥 What STON.fi returns for an asset
- Contract address and asset kind (Ton, Wton, Jetton).
- Display name, symbol, decimals and image URL under the meta object.
- Optional DEX price in USD, tags and popularity data.
- Wallet balance when you use a wallet-aware call.
🚀 Choose the query that fits your UI
- getAssets() when you need the full DEX list.
- getAsset(address) for a single known contract.
- queryAssets() for search terms plus liquidity or wallet conditions.
- getWalletAssets() when you want balances tied to a connected wallet.
⚡ Clean up the response for your frontend
Map each AssetInfoV2 into a small TokenOption that holds address, name, symbol, decimals, imageUrl, priceUsd and tags. Always fall back to symbol or a shortened address if displayName is missing, and use a local placeholder when no image exists.
Decimals decide how raw on-chain amounts become readable balances, so convert with BigInt rather than floating-point math. Never treat a familiar ticker as unique identity. Keep the contract address as the value you pass into swaps.
The real value is that STON.fi already normalizes the messy metadata so your token selector, portfolio view or swap interface stays simple and reliable.
Which STON.fi endpoint would you reach for first in a live search box? 👇
Tell us the toughest metadata edge case you have hit.
Not investment advice - research on your own! 🚀
$GRAM @STONfi DEX
STON.fi gives builders a clean HTTP API and TypeScript client so you can pull token names, symbols, decimals, images, prices and tags without decoding jetton cells yourself.
🔥 What STON.fi returns for an asset
- Contract address and asset kind (Ton, Wton, Jetton).
- Display name, symbol, decimals and image URL under the meta object.
- Optional DEX price in USD, tags and popularity data.
- Wallet balance when you use a wallet-aware call.
🚀 Choose the query that fits your UI
- getAssets() when you need the full DEX list.
- getAsset(address) for a single known contract.
- queryAssets() for search terms plus liquidity or wallet conditions.
- getWalletAssets() when you want balances tied to a connected wallet.
⚡ Clean up the response for your frontend
Map each AssetInfoV2 into a small TokenOption that holds address, name, symbol, decimals, imageUrl, priceUsd and tags. Always fall back to symbol or a shortened address if displayName is missing, and use a local placeholder when no image exists.
Decimals decide how raw on-chain amounts become readable balances, so convert with BigInt rather than floating-point math. Never treat a familiar ticker as unique identity. Keep the contract address as the value you pass into swaps.
The real value is that STON.fi already normalizes the messy metadata so your token selector, portfolio view or swap interface stays simple and reliable.
Which STON.fi endpoint would you reach for first in a live search box? 👇
Tell us the toughest metadata edge case you have hit.
Not investment advice - research on your own! 🚀
$GRAM @STONfi DEX
