Skip to main content
A token ID is a UUID that uniquely identifies a token across blockchains in Circle Wallets. The Wallets API uses the token ID anywhere it references a specific token, including balance lookups, transaction lists, and monitored token configuration. For each blockchain’s chain code, see Supported blockchains.
Arc Testnet uses USDC as its native gas token, so an Arc Testnet wallet’s USDC appears twice in the Wallets API: once as the native token and once as an ERC-20. Both entries reference the same underlying USDC balance. They aren’t separate assets, and gas payments don’t charge the wallet twice.

​
USDC token IDs

The following tables list the USDC token ID and contract address on each supported blockchain.

​
Mainnet

​
Testnet

​
EURC token IDs

The following tables list the EURC token ID and contract address on each supported blockchain.

​
Mainnet

​
Testnet

​
Native token IDs

The following tables list the native token ID on each supported blockchain.

​
Mainnet

​
Testnet

​
Find a token ID

The preceding tables provide a manual reference. The Wallets API also returns the token ID alongside each token a wallet holds (native tokens, USDC, other ERC-20s, and NFTs) in responses from:
Cache the token IDs your integration uses. Token IDs are stable, so a local lookup is faster than calling the Wallets API on every request.

​
Monitored tokens

By default, the Wallets API returns every token held in a wallet across balance, NFT, and transaction responses. Use monitored tokens to narrow that scope so the Wallets API only surfaces tokens your integration depends on (for example, to hide unrelated assets from end users). Token IDs are how you reference each token when managing the monitored list. Use the following endpoints to manage the monitored token list: Adding a token automatically sets the scope to SELECTED. To temporarily include every token in a single response, set includeAll=true on GET /wallets/{id}/balances, GET /wallets/{id}/nfts, or GET /transactions.