HYPERLIQUID:BTC. Build and test against those in the sandbox. Other
data is licensed to each user: futures prices come only from a trader’s own login at a provider
that carries them, and reach that trader in the trading app, or through a venue’s or a Connect
app’s backend acting for them. A Trading API key reads the public data alone.
Providers says which kind each provider supplies. Every read names the same symbols
the trading routes use.
What you can build
- A chart. Find the symbol, read how its prices are written, load its history, then stream live bars.
- Scrolling back through history. Ask for the bars before a point in time, and the answer says when there’s nothing older.
- A watchlist. Take quotes for up to 50 symbols in one call, answered in the order you asked.
- Several charts on one connection. One stream carries up to 24 instrument and timeframe pairs.
- Spreads. Write an expression over up to four instruments, such as
HYPERLIQUID:BTC/HYPERLIQUID:ETH, and it loads and streams like one instrument. - Correct prices without hard-coded rules. Tick size, price format, trading hours and holidays all come from the API.
- News and an economic calendar. Read headlines and calendar events, and follow each on its own stream.
Start with the limits
Read Get market-data limits once, before your first data call. It lists the timeframes you can ask for, how many bars and symbols one request can carry, and which asset classes this deployment serves, so your app can check a request before it sends it. The market data routes are limited to bursts of 120 requests, refilling at 30 a second. A request over the limit answers429 with a Retry-After header. Rate limits has the
details.
Next steps
Find symbols
Search the catalog and read the tick, price format and hours of one instrument.
Backfill history
Load a window of bars, scroll back through older ones, and chart spreads.
Stream live data
Follow live bars and the account, with reconnects that need no bookkeeping.
Build a front end
Put a chart and a trading screen on your own site, with your keys on your server.