Reference

Tokens whose symbol and decimals the API knows

The contracts enrichment can name and denominate. Anything outside this list falls back to 18 decimals and a null symbol, which is why an amount for an unlisted token may be wrong — check here before showing one.

get/v1/supported-tokens-registry

Request

  • Base URL: https://intelapi.publicaml.org
  • URL: https://intelapi.publicaml.org/v1/supported-tokens-registry
  • Auth: one of:
    • API key in header X-API-Key
    • none

Query parameters

chain'bitcoin' | 'ethereum' | 'bsc' | 'tron'

Which blockchain the address belongs to. Send one of the four values in the enum. The short forms used by the older clients (ETH, BTC, TRX, BNB) and any capitalisation are still accepted, but responses always echo the canonical spelling.

Getting this wrong is the single commonest integration bug: the same 0x-prefixed address exists on ethereum, bsc and tron and means a different wallet on each, so the chain is part of the identity, never a hint. If it does not match the address format the call fails with invalid_address_format, which names the chain the address does look like.

Response

The registry.

object required

Changes

No recorded changes to this operation across all 1 revision of this API.