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, to discover the hidden streams your account is entitled to, and to confirm which streams your account can access.

The response also surfaces useful metadata for each stream, such as the report schema version it uses, its market hours, and its expected decommission date, and more.

Endpoint

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

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

Sample request

GET /api/v1/discovery

Authentication

Data Streams Authentication is optional for the Discovery endpoint. It returns stream metadata, including which streams exist and their schema, not report data. However, authentication provides additional access to streams valid for your API key:

• 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.

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.

For example, this public request returns all live streams:

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

Query parameters

Query parameters are how you search the catalog. Use them to filter the response down to the streams you care about, for example, by asset, status, or network. Every parameter is optional; 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

Filter values

The string filters accept the values the catalog currently uses. The lists below are not exhaustive — the catalog grows over time, so new values may appear.

Asset class

asset_class is a broad asset category. The catalog currently uses:

Feed type

feed_type is a stream category. The catalog currently uses:

Attribute type

attribute_type is the kind of data reported. The catalog currently uses:

Stream status

The status filter distinguishes production streams from pre-production streams:

• live - production streams that are ready for production use.
• testing - pre-production streams used for validation.

Testing streams are visible without authentication. Omitting the status filter returns both live and testing streams, so filter explicitly with status=live to return only streams that are ready for production.

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

The following examples show common ways to filter the catalog.

All live streams

GET /api/v1/discovery?status=live

Crypto streams quoted in USD

GET /api/v1/discovery?asset_class=Crypto&quote_asset=USD&status=live

Multiple base assets

GET /api/v1/discovery?base_asset=BTC,ETH,SOL

Streams created after a date

GET /api/v1/discovery?created_after=2026-01-01&status=live

Live streams, including hidden ones your key can reach

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.

For accounts entitled to these streams, the hidden parameter retrieves their metadata:

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"

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.