Skip to main content
Perps Data is read-only market data for Polymarket’s perpetual-futures markets: funding rates, open interest, mark-versus-index basis, long/short account skew and detected liquidations, served over REST from https://partner-api.bravadotrade.com. It answers market-structure questions about the perp — what funding costs, how crowded a side is, where interest sits — without you running a venue indexer.
Perps Data is part of the Data API product: the same key, the same HMAC gate and the same credit model as /trader-analytics/*. Sign every request with your Data API credential (analytics.read) on an active paid plan, using HMAC authentication. Each successful response costs 1 credit, and the surface has its own per-key rate bucket. There is no separate Perps Data endpoint or key in Console. Coverage is Polymarket.
This is market data, not execution, and it is a different surface from the Polymarket Perps Trade API (/v2/trade/perps/*). These routes read market structure; they place no orders and need no trading scope. The figures are analytics-grade, not tax-grade — they describe the market, not a wallet’s book.

​
Why Bravado over reading the venue

The venue publishes this data, so this is not about access. It is about not building and running an indexer to normalise funding intervals, bucket open interest, recompute basis and reconstruct skew from account snapshots — and to keep them aligned with the same instrument identifiers as the rest of Bravado.

​
Endpoints

Funding history

Per-interval funding observations for one instrument, oldest first — the venue-published rate kept exact, plus its hourly-normalised and annualised forms.

Funding comparison

One symbol on the Polymarket perp against Binance, Bybit and Hyperliquid, interval-normalised. A venue missing from a complete window is named, never shown a zero rate.

Open-interest history

OHLC of open interest in contracts, plus the closing USD notional per bucket, at the interval you pick.

Basis

OHLC of mark, index and basis in basis points per bucket, at the interval you pick.

Long/short skew

Long and short account counts, exact contract sums and concentration — point-in-time or as a series of 1-minute bars — over the observed account universe.

Liquidations

Detected liquidations, oldest first, each carrying its evidence class. Indeterminate fields are null, never a fabricated zero.
GET /perps/book/asof is reserved and not yet available: it answers 404 NOT_IMPLEMENTED until the 1-second order-book layer (perps_book_1s) exists. Do not integrate against it yet.

​
Shared conventions

  • Base URL is https://partner-api.bravadotrade.com; every route lives under /perps.
  • Time parameters (from, to, at) accept RFC3339, unix seconds or unix milliseconds.
  • instrument is either the venue-native id (for example 6) or the canonical symbol (for example BTC), matching [A-Za-z0-9._-]{1,32}. The skew endpoint takes the venue-native id only.
  • Provenance is explicit. A value the venue did not publish is served as null with its reason, never as a fabricated 0 — oi_usd_close, premium_recomputed, each liquidation’s indeterminate fields, and the whole skew snapshot when none exists.
  • Empty windows are valid answers. A window the venue published nothing for returns an empty result, not an error.

​
Endpoints at a glance

The interval-dependent ranges for open interest and basis are 1m: 1 day, 5m: 7 days, 15m: 21 days, 1h: 90 days, 4h: 180 days, 1d: 400 days.

​
Errors

Every route signs and meters like the rest of the Data API, so it shares the product’s status codes:
  • Data API — the product this surface belongs to: wallet PnL, positions, history and Combos data on the same credential.
  • Polymarket Perps Trade API — placing orders on the same perpetual-futures markets (a separate, enterprise-only surface).
  • Market Data — realtime trades and order books over WebSockets.
  • API credits — how usage is metered.