Stream ID API

The Stream ID API provides programmatic access to Chainlink Data Streams feed IDs and supported network verifier proxy addresses, in plain text or JSON format suitable for tooling, agents, and automated workflows.

For Data Feeds proxy addresses (price feeds, SmartData, rates), see the Feed Address API.

Endpoints

Get stream IDs

GET https://docs.chain.link/api/streams/ids?type={category}

Returns stream feed IDs for the requested category. Stream IDs are universal — the same ID is valid across all supported networks.

Query parameters

Example requests

# Crypto stream IDs (ETH/USD, BTC/USD, etc.) — markdown
curl "https://docs.chain.link/api/streams/ids?type=crypto"

# Crypto streams — JSON
curl "https://docs.chain.link/api/streams/ids?type=crypto&format=json"

# All RWA streams (v8 Standard + v11 Advanced combined)
curl "https://docs.chain.link/api/streams/ids?type=rwa"

# RWA Standard only (v8)
curl "https://docs.chain.link/api/streams/ids?type=rwa&schema=v8"

# RWA Advanced only (v11 — extended trading hours)
curl "https://docs.chain.link/api/streams/ids?type=rwa&schema=v11"

# Exchange rate stream IDs — JSON
curl "https://docs.chain.link/api/streams/ids?type=exchangeRate&format=json"

Markdown response (truncated)

# Chainlink Data Streams: Data Streams — RWA

| Stream | Feed ID | Asset Class | Schema | Trading Hours |
|--------|---------|-------------|--------|---------------|
| AAPL/USD | `0x...` | Equities | v8 | Mon–Fri 9:30–16:00 ET |
| AAPL/USD | `0x...` | Equities | v11 | Mon–Fri 9:30–16:00 ET |
| EUR/USD  | `0x...` | Forex      | v8 | — |
...

JSON response (truncated)

{
  "type": "crypto",
  "label": "Data Streams — Crypto",
  "schemaFilter": null,
  "count": 237,
  "streams": [
    {
      "name": "BTC/USD",
      "feedId": "0x00039d9f...",
      "assetClass": "Crypto",
      "schema": "v3"
    },
    {
      "name": "AAPL/USD",
      "feedId": "0x000b313c...",
      "assetClass": "Equities — Regular Hours",
      "schema": "v11",
      "tradingHours": "Regular Hours (9:30am–4:00pm Mon–Fri ET)"
    },
    ...
  ]
}

The schema column is included in all responses. For categories with multiple schemas (e.g. rwa), both appear in the combined response. Use ?schema= to narrow to one. tradingHours is only present on streams with restricted market hours.

Get supported networks

GET https://docs.chain.link/api/streams/networks

Returns all networks supported by Chainlink Data Streams with verifier proxy contract addresses. Verifier proxies are shared across all categories and schemas — use the address for the network where your application is deployed. See Supported Networks for the full interactive list.

Query parameters

Example requests

curl "https://docs.chain.link/api/streams/networks"
curl "https://docs.chain.link/api/streams/networks?format=json"
curl "https://docs.chain.link/api/streams/networks?include=testnet&format=json"

JSON response (truncated)

{
  "mainnet": [
    {
      "network": "Arbitrum",
      "label": "Arbitrum Mainnet",
      "verifierProxy": "0x478Aa2aC9F6D65F84e09D9185d126c3a17c2a93C"
    },
    {
      "network": "Avalanche",
      "label": "Avalanche Mainnet",
      "verifierProxy": "0x79BAa65505C6682F16F9b2C7F8afEBb1821BE3f6"
    }
  ]
}

Markdown response (truncated)

# Chainlink Data Streams — Supported Networks

## Mainnet Networks

| Network | Label | Verifier Proxy |
|---------|-------|----------------|
| Arbitrum | Arbitrum Mainnet | `0x478Aa2aC9F6D65F84e09D9185d126c3a17c2a93C` |
| Avalanche | Avalanche Mainnet | `0x79BAa65505C6682F16F9b2C7F8afEBb1821BE3f6` |
| Base | Base Mainnet | `0xDE1A28D87Afd0f546505B28AB50410A5c3a7387a` |
...

Stream categories

Each type value maps to a stream category, matching the sections in the report schema overview. A category may contain streams that use more than one report schema.

The schema parameter accepts the version string as shown above. Schema version is read from source data, so new schemas released in future will appear in responses automatically.

Static snapshots

Pre-rendered snapshots of stream IDs for each category, baked at deploy time. Useful for offline tooling, RAG indexing, or any context where a live API call is not practical.

curl "https://docs.chain.link/data-feeds/feed-addresses/streamsCrypto.txt"
curl "https://docs.chain.link/data-feeds/feed-addresses/streamsRwa.txt"
curl "https://docs.chain.link/data-feeds/feed-addresses/streamsNav.txt"
curl "https://docs.chain.link/data-feeds/feed-addresses/streamsExRate.txt"
curl "https://docs.chain.link/data-feeds/feed-addresses/streamsBacked.txt"

Snapshots reflect data as of the last site deployment. For always-current data, use the live endpoint.

Notes

• Stream IDs are universal and do not change per network. The same feed ID is used whether your application is on Arbitrum, Avalanche, Base, or any other supported network.
• To verify a report onchain, use the verifier proxy for the network where your application is deployed. See Verify report data onchain.
• To fetch reports offchain, see the Getting Started guide and SDK tutorials.
• For background on how Data Streams work, see Architecture and Concepts.
• Responses match exactly what is shown in the interactive stream ID tables in the docs.
• Data is sourced from the same backend used by the interactive stream ID tables in the docs, cached daily.