Discovery Endpoint

The Discovery endpoint returns the catalog of Data Streams, including each stream's ID, asset pair, report schema version, and status. Use it to look up stream IDs programmatically instead of hardcoding them, and to confirm which streams your account can access.

Endpoint

The Discovery endpoint is part of the Data Streams REST API and lives on the same host:

Description	Mainnet URL
Discovery endpoint	https://api.dataengine.chain.link/api/v1/discovery

GET /api/v1/discovery

Authentication

Unlike the other REST API routes, the Discovery endpoint does not require authentication. It returns stream metadata — which streams exist and how they are configured — not report data.

• Without authentication, the endpoint returns the streams Chainlink lists publicly.
• With authentication, it also returns the streams your API key is entitled to, including any hidden streams provisioned for your account.

Being listed is not the same as having access. Every stream in the response, public or hidden, still requires credentials and an entitlement to that stream before you can retrieve its reports.

Authenticate the same way as any other Data Streams REST request, by sending the three HMAC headers described on the Data Streams Authentication page. If you use a Data Streams SDK, authentication is handled for you.

Public request:

curl "https://api.dataengine.chain.link/api/v1/discovery?status=live"

Query parameters

Every parameter is an optional filter. Omitting one means no restriction on that field.

• String filters accept a comma-delimited list and match any of the supplied values, compared case-insensitively. For example, base_asset=btc,eth returns both BTC and ETH streams.
• Different parameters combine with AND. For example, asset_class=Crypto&quote_asset=USD returns only crypto streams quoted in USD.
• Unrecognized parameters are ignored.

Metadata filters

Date filters

Date filters take a YYYY-MM-DD date with no time component, and are strict: after and before exclude the date itself. A value that isn't a plain date returns HTTP 400.

Examples

GET /api/v1/discovery?status=live
GET /api/v1/discovery?asset_class=Crypto&quote_asset=USD&status=live
GET /api/v1/discovery?base_asset=BTC,ETH,SOL
GET /api/v1/discovery?created_after=2026-01-01&status=live
GET /api/v1/discovery?status=live&hidden=true

Hidden streams

Chainlink often launches new streams privately, before they are announced or made generally available. These streams are marked as hidden: they are excluded from the public Chainlink documentation and from the default Discovery endpoint response, but they are fully functional for the accounts provisioned to use them.

The hidden parameter is how you see those streams:

curl "https://api.dataengine.chain.link/api/v1/discovery?hidden=true&status=live" \
  -H "Authorization: $API_KEY" \
  -H "X-Authorization-Timestamp: $TIMESTAMP" \
  -H "X-Authorization-Signature-SHA256: $SIGNATURE"

Hidden streams are gated on entitlement, not on the parameter. Setting hidden=true on an unauthenticated request, or on a request signed with a key that has no hidden entitlements, returns the same public catalog. Authenticating with an entitled key is what reveals them.

Response

The response is a JSON object with a single feeds array:

{
  "feeds": [
    {
      "assetClass": "Crypto",
      "assetName": "Render",
      "baseAsset": "RENDER",
      "quoteAsset": "USD",
      "attributeType": "CexPrice",
      "feedType": "Crypto",
      "createdAt": "2024-09-19T17:05:44.554814Z",
      "decommissionedAt": null,
      "expectedDecommissionAt": null,
      "feedId": "0x00034e3ab3a1c0809fe3f56ffe755155ace8564512cbc3884e9463dba081c02a",
      "marketHours": "Crypto",
      "name": "RENDER/USD-Streams-CexPrice",
      "networkType": "mainnet",
      "schemaVersion": "V3",
      "serviceLevel": "Streams",
      "status": "live"
    }
  ]
}

Schema

The Discovery endpoint returns the schema version a stream uses, not the report schema itself. To find the fields a given schemaVersion contains and how to decode them, see the Report Schemas page.

Errors and caching

Errors return a JSON object with a single error field describing the problem.

Successful responses are cacheable and are served with Cache-Control: public, max-age=300. Expect a newly launched stream to take up to five minutes to appear.