Skip to main content
POST
/
v1
/
w3s
/
config
/
entity
/
monitoredTokens
Set monitored tokens
curl --request POST \
  --url https://api.circle.com/v1/w3s/config/entity/monitoredTokens \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "tokenIds": [
    "a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11"
  ]
}
'
{
  "data": {
    "tokens": [
      {
        "id": "c4d1da72-111e-4d52-bdbf-2e74a2d803d5",
        "blockchain": "MATIC-AMOY",
        "isNative": true,
        "updateDate": "2023-01-01T12:04:05Z",
        "createDate": "2023-01-01T12:04:05Z",
        "name": "<string>",
        "decimals": 123,
        "symbol": "<string>",
        "tokenAddress": "0xca9142d0b9804ef5e239d3bc1c7aa0d1c74e7350"
      }
    ]
  }
}

Documentation Index

Fetch the complete documentation index at: https://developers.circle.com/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
Authorization
string
header
required

Circle's API Keys are formatted in the following structure "PREFIX:ID:SECRET". All three parts are required to make a successful request.

Body

application/json

Request body

​
tokenIds
string<uuid>[]
required

The list of tokens to add to the monitored tokens list. When fetching wallet balances, only these tokens will be shown by default.

Minimum array length: 1

System-generated unique identifier of the resource.

Example:
["a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11"]

Response

Success and no update happened

​
data
object