Chain Operations | Ondo

No RPC call is made: Both operations here are plain REST GETs served by Ondo's own backend (which indexes the chain for you) — not a direct blockchain RPC call. That means no node/RPC provider credential is needed for these two operations.

getBalances

Token balances on a given chain.

Field	Type	Required	Description
`chainId`	text	✓ Yes	Target chain ID.
`userAddress`	text	No	Filter to a single holder address.
`tokenAddress`	text	No	Filter to a single token contract.

Unbounded response risk: If neither userAddress nor tokenAddress is supplied, the operation returns balances across all users/tokens on the chain. Always supply at least one filter in production workflows.

Example response:

{
  "chainId": "1",
  "balances": [
    { "holderAddress": "0x1234...", "balance": "500.000000000000000000" }
  ],
  "count": 1
}

getTokenInfo

On-chain token contract metadata.

Field	Type	Required	Description
`chainId`	text	✓ Yes	Target chain ID.
`tokenAddress`	text	✓ Yes	Token contract address.

Example response:

{
  "tokenAddress": "0xabc...",
  "tokenName": "Ondo Tokenized AAPL",
  "tokenSymbol": "AAPLon",
  "tokenDecimals": 18,
  "tokenSupply": "1000000.000000000000000000"
}

Tip: Combine getTokenInfo with getAddresses to resolve a GM symbol to a contract address, then look up the deployed token's live supply and decimals in one extra call.