Asset and Chain
9 min
use these read only endpoints to discover the assets and chains currently enabled for the api user's organization do not hard code the returned list list assets get /api/external/assets/ returns the organization's supported asset representations the same symbol can appear more than once when it exists on multiple blockchains request example no request body or sdk parameters {} response interface asset { name string; symbol string; blockchain string; logourl? string; details? unknown; } type response = asset\[]; \[ { "name" "usd coin", "symbol" "usdc", "blockchain" "ethereum", "details" { "tokenaddress" "0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48" } }, { "name" "usd coin", "symbol" "usdc", "blockchain" "solana", "details" { "tokenaddress" "epjfwdd5aufqssqem2qn1xzybapc8g4weggkzwytdt1v" } } ] details is chain specific metadata treat unrecognized keys as optional and use symbol together with blockchain as the asset/network pair javascript sdk getassetsdata() promise\<asset\[]> list supported chains get /api/external/assets/supported chains/ returns the chain identifiers and display metadata enabled for the organization request example no request body or sdk parameters {} response interface chaindata { value string; label string; } type response = chaindata\[]; \[ { "value" "ethereum", "label" "ethereum", }, { "value" "solana", "label" "solana", } ] javascript sdk getsupportedchains() promise\<chaindata\[]> use value wherever an endpoint expects a chain identifier