Feeds with live status
Every feed with both of its IDs, its category and its live value. Unlike the Hermes routes, a degraded or closed feed is shown live here, with its status.
Query Parameters
Keep one category, such as crypto or equity.
Response Body
application/json
text/plain
curl -X GET "https://example.com/v1/feeds"[ { "id": "string", "pyth_id": "string", "symbol": "string", "category": "crypto", "attributes": { "property1": "string", "property2": "string" }, "live": { "status": "trading", "price": "string", "conf": "string", "expo": 0, "publish_time": 0, "timestamp_ms": 0, "served_publish_time": 0, "sources": 0 } }]Price at a time (v1) GET
The first update of one feed at or after `publish_time`.
Pyth ID to Astra ID map GET
Every feed Astra serves, once, sorted by symbol, with its Astra ID and its Pyth-compatible ID when it has one. Paste your Pyth IDs into `pyth_ids` to see which ones Astra serves: the Hermes routes accept those IDs as they are, so a feed found here needs no change in the client. `missing` lists the requested IDs Astra does not serve, lower-case without `0x`. With neither `pyth_ids` nor `astra_ids` the whole list is returned, without `missing`. With either, only the matching feeds are returned, plus `missing`. `pyth_ids` matches Pyth-compatible IDs only and `astra_ids` Astra IDs only; both may be combined. `category` narrows the items and never adds to `missing`. The answer changes only on a deploy: it may be cached for an hour, and the unfiltered list carries an `ETag`. Send at most 200 IDs per request, `pyth_ids` and `astra_ids` together; longer URLs are rejected before they reach Astra. For more IDs, use several requests.