AVavaprotocol
Tokens

Retrieve ERC-20 token metadata

Changed on

Partner-gated public-ish chain data. Requires a partner assertion with scope: read (X-Partner-Assertion). A user Bearer JWT alone is not sufficient.

get/tokens/{address}

Request

  • Base URL
    https://api.avaprotocol.org/api/v1
  • Auth
    API key in header X-Partner-Assertion

Query parameters

chainIdinteger

The chain to operate on (a single value). Omit to use the aggregator default (the request's JWT aud chain, then the gateway default).

Response

Token metadata (found: false if unknown).

foundboolean required
addressstring

Lowercase or checksummed hex EOA / contract address.

chainIdinteger

Numeric chain ID (e.g. 11155111 for Sepolia, 8453 for Base). On chain-aware trigger/node configs this is required and must be a configured chain; on query/filter params it is optional.

namestring
symbolstring
decimalsinteger
source'whitelist' | 'rpc' | 'cache'

Example response

{
  "address": "0x82F2Dd9a552a69f2ceD7Ff2D05c43aB8430158FB",
  "chainId": 11155111
}

Changes

  • 6b505ebcf3f7Revision changes
    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status

  • 4ebf07931311Revision changes
    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status