> ## Documentation Index
> Fetch the complete documentation index at: https://docs.allium.so/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Unified market data — reference, pricing, and perps primitives across trading venues, blended from on-chain and off-chain sources.

<Warning>
  **Alpha** — The Market Data API is in alpha. Schema and response format may change. To request access, [contact us](https://www.allium.so/contact) or reach out to your account manager.
</Warning>

Allium's Market Data API provides a single interface for navigating tradeable markets — reference metadata, latest and historical pricing, and perps primitives (funding, open interest, liquidations) — across trading venues.

## Key Features

<CardGroup cols={3}>
  <Card title="Unified Market Reference" icon="magnifying-glass">
    List, filter, and search markets across venues and instrument types with a
    single canonical `market_id`.
  </Card>

  <Card title="Pricing & Candles" icon="chart-candlestick">
    Latest price snapshots and historical OHLCV candles at standard
    institutional intervals.
  </Card>

  <Card title="Perps Primitives" icon="chart-line">
    Funding rates, open interest, and liquidations for perpetual markets.
  </Card>
</CardGroup>

## 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`, `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](/api/developer/market-data/assets).*

`instrument_type` is one of `perp` or `spot` today. `future` and `option` are reserved for future use.

## Supported venues

<Info>
  **Hyperliquid** is the only venue available today. Additional CEX and DEX
  venues (e.g. Binance, dYdX, Uniswap) are **coming soon** — to request
  prioritization of a specific venue, reach out to your account manager.
</Info>

The endpoint surface does not change as venues are added — the `venue` dimension simply grows, and the same `market_id` shape extends to new venues.

## Conventions

<Tabs>
  <Tab title="Decimals as strings">
    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.
  </Tab>

  <Tab title="Timestamps">
    Timestamp inputs are parsed as ISO 8601; a naive datetime (no offset) is
    treated as **UTC**. Timestamp outputs always carry an explicit `+00:00`
    suffix.
  </Tab>

  <Tab title="Pagination">
    List endpoints use opaque **cursor** pagination. When a response includes a
    `cursor`, pass it back on the next request to fetch the following page; its
    absence means there are no more results.
  </Tab>
</Tabs>

## Authentication

All endpoints require an API key passed in the `X-API-KEY` header. The base URL is `https://api.allium.so`.

```bash theme={null}
curl --url "https://api.allium.so/api/v1/markets?venue=hyperliquid&instrument_type=perp" \
  --header "X-API-KEY: YOUR_API_KEY"
```