Advanced POST requests allow you to query for several tokens on multiple networks within the same request.
Token Ids
Unless specified otherwise, all advanced POST requests accept an array of token_ids that represents a list of tokens for which the data will be queried.
For example below are the addresses for the YFI token for different networks:
| Address | Network |
|---|---|
| 0x0bc529c00c6401aef6d220be8c6ea1667f6ad93e | Ethereum (1) |
| 0xda537104d6a5edd53c6fbba9a898708e465260b6 | Polygon (137) |
| 0x29b0da86e484e1c0029b56e817912d778ac0ec69 | Fantom (250) |
The token id array corresponding to the token above is:
["0x0bc529c00c6401aef6d220be8c6ea1667f6ad93e-1",
"0xda537104d6a5edd53c6fbba9a898708e465260b6-137",
"0x29b0da86e484e1c0029b56e817912d778ac0ec69-250"]
token_idsare case insensitive
Relevant Endpoints:
Get average price by token ids (advanced)
Get swaps by token ids (advanced)
Get pool events by token ids (advanced)
Use cases:
Note that the ERC20 tokens of each project can have several representations on the same chain. For example a token can be bridged through multiple bridges (for example Celer and Wormhole). Using token ids allows you to specify exactly which tokens you want to include in your API request.
In the same way, many projects will stake a user's ERC20 token and in exchange provide a wrapped version of that same token which should then usually be considered as a derivative of the original token. The extent to which a derivative token should be included in the original token's volume, price and other aggregate calculations depends on the derivative token's functionality/constraints and on your own personal view.
For example, aBNBc is a reward-bearing version of the WBNB asset. While these tokens are different, it's possible to consider aBNBc trading should be accounted for when discussing WBNB trading.