Asset Addresses & Metadata | Ondo

Why this matters: These operations bridge Ondo's off-chain pricing data to on-chain contract addresses — feed the returned addresses into a chain-specific node (Ethereum, BNB, Solana) or into Chain Operations on this node.

getAllAddresses

Contract addresses for all assets, across every supported network (no parameters).

Example response:

{
  "assets": [
    { "symbol": "AAPLon", "addresses": [
        { "networkChainId": "1", "address": "0xabc...", "decimals": 18 },
        { "networkChainId": "137", "address": "0xdef...", "decimals": 18 }
    ] }
  ],
  "count": 412
}

getAddresses

Contract addresses for a single asset — the narrow, workflow-friendly form of getAllAddresses.

Field	Type	Required	Description
`symbol`	text	✓ Yes	GM asset symbol.

Example response:

{
  "symbol": "AAPLon",
  "addresses": [
    { "networkChainId": "1", "address": "0xabc...", "decimals": 18 }
  ]
}

getAllMetadata

Market-data-provider cross-references and tags for all assets (no parameters). This is provider cross-referencing (CoinGecko/CoinMarketCap IDs, tags), not descriptive text.

Example response:

{
  "assets": [
    { "symbol": "AAPLon", "ticker": "AAPL", "coingeckoId": "ondo-tokenized-aapl",
      "coinmarketcapId": "34521", "tags": ["equity", "us-stock"],
      "addresses": [ { "networkChainId": "1", "address": "0xabc...", "decimals": 18 } ] }
  ],
  "count": 412
}

Tip: Call getAllAddresses or getAllMetadata once and cache the result — contract addresses and provider IDs rarely change, so re-fetching them on every workflow run is usually unnecessary load.