Prices over an interval
Updates from publish_time to publish_time + interval, inclusive, one PriceUpdate per second,
oldest first. ema_price equals price on historical routes. At most 100 distinct feeds,
which keeps the URL under the edge's length limit.
Path Parameters
Unix time in seconds.
0 <= value <= 4294967295Length of the window in seconds, at most 60.
0 <= value <= 60Query Parameters
Feed IDs, repeated (ids[]=…&ids[]=…). ids is accepted too. The server accepts at most 500 per request, and 100 distinct feeds on historical routes. Send at most 200 IDs per request; longer URLs are rejected before they reach Astra. For more feeds, use several requests or subscribe over WebSocket, where IDs travel in the message body.
items <= 500The same as ids[], for clients that send the name without brackets. Both may be combined, and count together. Send at most 200 IDs per request; longer URLs are rejected before they reach Astra. For more feeds, use several requests or subscribe over WebSocket, where IDs travel in the message body.
Encoding named in binary.encoding on the v2 routes. The data array is always empty. Validated and ignored on the v1 routes.
"hex"Value in
- "hex"
- "base64"
Include the parsed prices on the v2 routes. Validated and ignored on the v1 routes.
trueDrop unknown IDs instead of answering 404, on the v2 routes. Validated and ignored on the v1 routes.
falseUpdate cadence of the SSE stream and the WebSocket. A fixed-rate channel sends a feed at most once per tick, only when it changed. fixed_rate@50ms is refused. Validated and ignored on the other routes.
"fixed_rate@1000ms"Value in
- "real_time"
- "fixed_rate@200ms"
- "fixed_rate@1000ms"
On the SSE stream, send only the first update of each second. Validated and ignored elsewhere.
falseInclude metadata, on the v1 routes. Validated and ignored on the v2 routes.
falseInclude vaa, which is always the empty string, on the v1 routes. Validated and ignored on the v2 routes.
falseOn the interval route, keep only the first update of each feed in each second. Validated and ignored elsewhere.
trueAccepted for Hermes compatibility. Updates are always ordered, so it changes nothing.
falseResponse Body
application/json
text/plain
text/plain
text/plain
text/plain
application/problem+json
curl -X GET "https://example.com/v2/updates/price/0/0?ids%5B%5D=string"[ { "binary": { "encoding": "hex", "data": [] }, "parsed": [ { "id": "string", "price": { "price": "string", "conf": "string", "expo": 0, "publish_time": 0 }, "ema_price": { "price": "string", "conf": "string", "expo": 0, "publish_time": 0 }, "metadata": { "slot": 0, "proof_available_time": 0, "prev_publish_time": 0 } } ] }]Prices at a time GET
The first update of each feed at or after `publish_time`. At most 100 distinct feeds, which keeps the URL under the edge's length limit.
Stream prices (WebSocket) GET
The Hermes WebSocket protocol. Open the socket with a `GET` upgrade, then send JSON text messages: - `{"type":"subscribe","ids":[…],"verbose":false,"binary":false,"ignore_invalid_price_ids":false}` is answered `{"type":"response","status":"success"}`, then the last value of each feed and every later update arrive as `{"type":"price_update","price_feed":{…}}`. - `{"type":"unsubscribe","ids":[…]}` is answered the same way. - A malformed message, an unknown type, an unknown or malformed ID, or more than 500 IDs is answered `{"type":"response","status":"error","error":"…"}`; the socket stays open. IDs travel in the message body, so a subscription is not bound by the URL length: this is the way to follow more than 200 feeds on one connection. `verbose` adds `metadata` to each `price_feed`, `binary` adds an empty `vaa`. `allow_out_of_order` is accepted and changes nothing. The server pings every 30 seconds and closes the socket after 24 hours (1000), when the client sends more than 5 messages per second with a burst of 20 or stops reading (1008), and when it restarts (1001). A message is at most 64 KiB.