Many of Blockpour's API endpoints accept a token parameter. Unless otherwise specified the token parameter can be either a token address or a token symbol.
For example pool snapshots for the YFI token on Ethereum can be queried as follows:
https://services.blockpour.com/api/pools/snapshots/reserves/token/YFI?network=ethereum
https://services.blockpour.com/api/pools/snapshots/reserves/token/0x0bc529c00c6401aef6d220be8c6ea1667f6ad93e?network=ethereum
Tokens on multiple chains.
Mapping tokens to symbols and multiple chains is complex.
An ERC20 token for a project on Ethereum can have several corresponding ERC20 tokens on a different chain if it is mapped through multiple bridges (for example Celer and Wormhole)
Additionally the same symbol is often by multiple used ERC20 tokens.
When querying by symbol, the data corresponding to the most traded token on a given network will be returned. In some rare cases, several tokens might be traded equally so we recommend using the token addresses for production applications
To quickly verify that your symbol is mapping to the correct address, you can use the token endpoint to verify that you are indeed querying the correct token.
For example to verify you have the correct DAI address on Optimism:
https://services.blockpour.com/api/tokens/DAI?network=optimism
The first token (most traded token) returned by this API query. will map to the given symbol.
Using token addresses is recommend for production applications
For production applications we recommend using token addresses to remove all ambiguity as to the data you are querying.
If you need to query data for tokens on multiple chains, we recommend using the advanced endpoints (POST requests)
Get swaps by token ids (advanced)
Get token average price (advanced)
Get pool events by token ids (advanced)