Key Features
Unified Market Reference
List, filter, and search markets across venues and instrument types with a
single canonical
market_id.Pricing & Candles
Latest price snapshots and historical OHLCV candles at standard
institutional intervals.
Perps Primitives
Funding rates, open interest, and liquidations for perpetual markets.
Resource model
Market data is organized around two resources:- Market — a tradeable instrument on a specific venue, keyed by a canonical slug
{venue}:{instrument_type}:{pair}, e.g.hl:perp:BTC-USDC,dydx:perp:ETH-USD,hl:spot:HYPE-USDC. - Asset — a canonical entity (e.g.
asset:bitcoin) that aggregates a token across all of its deployments and markets. Asset-keyed endpoints are coming soon.
instrument_type is one of perp, spot, or pred today. pred identifies Hyperliquid prediction markets (hl:pred:<id>) — they don’t appear in market listings and carry candle data only. future and option are reserved for future use.
Supported venues
GMX v2 is one venue per chain — the same market on two chains is two markets (e.g.
gmx-arbitrum:perp:BTC-USD and gmx-avalanche:perp:BTC-USD).
The endpoint surface is identical for every venue. Some series are still backfilling for the newest venues: Jupiter and GMX currently serve market metadata and candles. Their price snapshots, funding, and open interest have no data yet, so those endpoints return 404 (price) or an empty items array (timeseries) until the ingestion lands — a 404 from a price endpoint means “no data in the freshness window”, not “unknown market”.
More venues are coming soon — major CEX spot venues (Binance, Coinbase,
Kraken, and others) are already in Allium’s ingestion pipeline and will be
exposed through this API. To request prioritization of a specific venue,
reach out to your account manager.
venue dimension simply grows, and the same market_id shape extends to new venues.
Conventions
- Decimals as strings
- Timestamps
- Pagination
All numeric response fields are returned as JSON strings to preserve
precision. Several values (notional, open interest in base units) exceed
JSON’s
2^53 safe-integer range, so parsing them as numbers would silently
round. Parse them with an arbitrary-precision decimal type.Authentication
All endpoints require an API key passed in theX-API-KEY header. The base URL is https://api.allium.so.