Endpoints
We have bundled the most frequently requested metadata and return it from a single endpoint:
/v1/tokens/<chain id>/<token address>
This endpoint will return a JSON dictionary that looks like this:
{
"chainId": 1,
"blockNumber": 15640049,
"blockTimestamp": 1664467199,
"tokenAddress": "0x7fc66500c84a76ad7e9c93437bfc5ac33e2ddae9",
"name": "Aave Token",
"symbol": "AAVE",
"decimals": 18
}
All other metadata endpoints include the name of the metadata requested. Note that the bundled values returned above can also be retrieved individually. We therefore end up with the following metadata endpoints:
Name (linked to formal API docs) | Endpoint |
|---|---|
/v1/tokens/<chain id>/<token address>/name | |
/v1/tokens/<chain id>/<token address>/symbol | |
/v1/tokens/<chain id>/<token address>/logo | |
/v1/tokens/<chain id>/<token address>/decimals | |
/v1/tokens/<chain id>/<token address>/creation-block | |
/v1/tokens/<chain id>/<token address>/abi |
The ABI endpoint requires a bit more explanation as it also returns other pieces of information that will be useful to developers using the ABIs.
The following call, a request for the AAVE token ABI
https://gateway.staging.credmark.com/v1/tokens/1/0x7fc66500c84a76ad7e9c93437bfc5ac33e2ddae9/abi
will return the following:
{
"chainId": 1,
"blockNumber": 15631397,
"blockTimestamp": 1664362799,
"tokenAddress": "0x7fc66500c84a76ad7e9c93437bfc5ac33e2ddae9",
"abi": [ <the entire ABI> ],
"isTransparentProxy": true,
"proxyImplementationAddress": "0xc13eac3b4f9eed480045113b7af00f7b5655ece8"
}
The key isTransparentProxy will be set to "true" or "false" depending on whether or not the contract can only be reached through a proxy. If the value is "true", the key proxyImplementationAddress will hold the proxy's address.
Last modified 9mo ago