The Blockdeamon API Suite provides access to multiple blockchain assets across multiple protocols. Information on assets is returned by Blockdeamon API Suite endpoints when you query accounts, blocks, and transactions.

For some of the supported protocols, multiple currencies and tokens are available. In this case, you can filter the results by the asset. To learn more, see the Filtering by Asset section and the examples below.

In the table below, you will find the full list of available currencies and tokens. The Path column contains asset paths used for filtering by asset.

Filtering by Asset

Some of the Blockdeamon API Suite endpoints support a query parameter allowing you to filter results by asset:

• parameter: assets
• value: an asset path or a comma-separated list of paths

The path structure for getting native coins is the following:

• {protocol}/native/{symbol}
• e.g. ethereum/native/eth

The path for getting tokens and other assets varies from protocol to protocol.

In the sections below, you will find examples of filtering by asset. Please note that only protocols for which the Blockdeamon API Suite supports multiple assets are included.

Supported endpoints

• GET Balances of Address
• GET Transactions of Address
• POST Balances of Addresses
• GET All Transactions

Algorand Examples

The path for the ALGO coin is the following:

• algorand/native/algo

Other assets are identified by numeric ID:

• algorand/asset/{id}

The Blockdeamon API Suite supports all Algorand standard assets; some examples are:

For example, to get the ALGO and USD balances of a given Algorand Mainnet address, use the assets parameter with the following values:

• algorand/native/algo
• algorand/asset/25077

svc.blockdaemon.com/universal/v1/algorand/mainnet/account/QA75IQ76F6H2T55G65BY7BPLF5QNWSLT5XGI62COZSYB4ZQ3MSKI3EQ25A?assets=algorand/native/algo,algorand/asset/25077

Learn more about the endpoint: GET Balances of Address.

Ethereum Examples

The path for the ETH coin is the following:

• ethereum/native/eth

ERC-20 tokens are identified by contract hash:

• ethereum/contract/{contract_hash}/erc-20

The Blockdeamon API Suite supports all ERC-20 tokens; some examples are:

For example, to get the ETH and USDT of a given Ethereum Mainnet address, use the assets parameter with the following values:

• ethereum/native/eth
• ethereum/contract/0xdac17f958d2ee523a2206206994597c13d831ec7/erc-20

svc.blockdaemon.com/universal/v1/ethereum/mainnet/account/0x3cd751e6b0078be393132286c442345e5dc49699?assets=ethereum/native/eth,ethereum/contract/0xdac17f958d2ee523a2206206994597c13d831ec7/erc-20

Learn more about the endpoint: GET Balances of Address

Solana Examples

The path for the SOL coin is the following:

• solana/native/sol

SPL tokens are identified by pubkey:

• solana/mint/{pub_key}

The Blockdeamon API Suite supports all SPL tokens; some examples are:

For example, to get the SOL and PLD balances of a given Solana Mainnet address, use the assets parameter with the following values:

• solana/native/sol
• solana/mint/2cJgFtnqjaoiu9fKVX3fny4Z4pRzuaqfJ3PBTMk2D9ur

svc.blockdaemon.com/universal/v1/solana/mainnet/account/BkJfuow72HkBGZMNGJQDwiPYmjvyu9DsgWxaFBVP5o2X?assets=solana/native/sol,solana/mint/2cJgFtnqjaoiu9fKVX3fny4Z4pRzuaqfJ3PBTMk2D9ur

Learn more about the endpoint: GET Balances of Address

Stellar Examples

The path for the XLM coin is the following:

• stellar/native/xlm

Other assets are identified by code (symbol):

• stellar/credit_alphanum4/{code}
• stellar/credit_alphanum12/{code}

Stellar supports two code types, 4- and 12-character maximum; some examples are:

For example, to get the XLM and MATIC balances of a given Stellar Mainnet address, use the assets parameter with the following values:

• stellar/native/xlm
• stellar/credit_alphanum12/matic

svc.blockdaemon.com/universal/v1/stellar/mainnet/account/GBIBSQ36BXMS2N6HIFLWGU3K2G7XJZIWI2R4GEBCJAOWIELJBRXVFH5J?assets=stellar/native/xlm,stellar/credit_alphanum12/matic

Learn more about the endpoint: GET Balances of Address