Funding rate is the periodic payment perpetual futures traders make to each other to keep a contract's price anchored to its underlying spot price. It's a real, tradeable number — the basis of cash-and-carry and funding-arbitrage strategies, a signal of crowd positioning (persistently positive funding usually means longs are paying shorts, a proxy for leveraged long demand), and a cost that eats directly into any perpetuals position held across a funding interval. Getting clean historical funding data across more than one venue at a time is still a surprisingly specific need that most general market-data providers don't serve well.
Convex Lake shipped a dedicated funding-rate endpoint on 2026-11-02. Here's exactly what it covers and how to query it.
What /funding actually covers
Per Convex Lake's own API documentation, GET /funding returns perpetual funding-rate CSVs across five venues: Binance, Hyperliquid, Deribit, OKX, and Bybit.
| Parameter | Required | What it does |
|---|---|---|
exchange | Yes | Venue name |
ticker | No | Instrument, e.g. BTC, ETH, or BTCUSDT — short names resolve to the venue's file. Omit to list available files |
date | No | YYYY-MM-DD — returns only rows from that UTC day |
presign | No | 1 returns a JSON time-limited download link instead of the file |
expires | No | Link lifetime in seconds when presign=1 (60–3600, default 900) |
Documented example requests:
GET /funding?exchange=binance
GET /funding?exchange=binance&ticker=BTC
GET /funding?exchange=bybit&ticker=ETH&date=2026-10-20
Exact symbol coverage per venue, historical depth, and update frequency aren't published on the docs page at time of writing — check convexlake.com/docs directly for the current reference before building against it, since this is one of the newest endpoints in the API.
One file per instrument, not daily batches
This is the detail worth knowing before you build a pipeline against it: unlike most of Convex Lake's other data endpoints, which deliver daily csv.gz batches, /funding stores data as one continuously growing file per instrument — funding/{exchange}/{instrument}.csv, with no date-based folder structure. Pulling exchange=binance&ticker=BTC with no date filter gets you the entire available history for that instrument in a single file, rather than requiring you to stitch together daily files yourself.
The date parameter still works if you only want one UTC day's worth of rows, filtered server-side rather than requiring you to download the full file and filter locally.
How downloads actually work
There's a real mechanical difference depending on whether you pass date:
- No
datefilter (full file): the request redirects to a time-limited presigned storage link (as of a 2026-11-04 update). Most HTTP clients — Pythonrequests, JSfetch/axios, browsers — follow this automatically. Plaincurlneeds-O -J -Lto follow the redirect and still name the file correctly. - With a
datefilter (one day's rows): the response streams the filtered rows directly, no redirect involved.
presign=1 is also supported directly — pass it to get a JSON response (download_url, expires_in) instead of either behavior above, useful if you want to hand off the actual download to something else in your pipeline rather than following a redirect yourself.
Access
Free-tier API keys read from a sample data store that doesn't include any funding files — funding-rate data requires a paid tier. Check convexlake.com/docs for the current tier requirement before assuming a specific plan covers it.
Common research use cases
Cross-venue funding comparison. With Binance, Hyperliquid, Deribit, OKX, and Bybit all under one schema and one endpoint, comparing funding-rate behavior for the same underlying across a centralized order-book venue (Binance, OKX, Bybit, Deribit) and a fully on-chain one (Hyperliquid) is a single pipeline rather than five separate integrations.
Funding-rate arbitrage and basis research. Persistent funding-rate divergence between venues for the same instrument is the raw signal behind funding-arbitrage and basis-trading strategies — having clean, comparable history across venues is the actual prerequisite for backtesting any of that honestly.
Combining with orderbook and candle data. /funding sits alongside Convex Lake's existing /orderbook and /candles endpoints for several of these same venues (Binance, Hyperliquid, Deribit, OKX all have perpetuals orderbook coverage), so a funding-rate time series can be joined against order-book depth or price action for the same instrument and date range without switching data sources.
Data quality pitfalls to watch for
This is a brand-new endpoint. It shipped 2026-11-02 — expect documentation (symbol lists, historical depth, update cadence) to keep filling in over the following weeks. Verify directly against the live docs before locking in integration assumptions.
Row schema isn't published. The docs confirm timestamp_ms is used for the date filter, but don't publish a full column list for the funding CSVs themselves. Check a sample file via /info or a direct unfiltered pull before assuming field names.
Free keys get nothing here. Unlike some other endpoints with sample-store access on free tiers, /funding isn't included in the free sample data — confirm your plan covers it before integrating.
FAQ
Does Convex Lake have historical funding rate data?
Yes — GET /funding, covering Binance, Hyperliquid, Deribit, OKX, and Bybit, launched 2026-11-02.
How is funding data delivered — daily files or one file per instrument?
One continuously growing CSV per instrument (funding/{exchange}/{instrument}.csv), not daily batches like most other Convex Lake endpoints. Use the optional date parameter to filter to a single UTC day server-side.
Does /funding support presigned download links?
Yes — pass presign=1 for a JSON response with a time-limited download link, or omit it and follow the default behavior (a redirect to a presigned link for full-file requests, or a direct stream for date-filtered requests).
Is funding rate data available on the free tier? No — free-tier keys read from a sample store that doesn't include funding files. Check the docs for the current paid-tier requirement.
What's the historical depth and update frequency for funding data? Not published on the docs page as of this writing. Check convexlake.com/docs directly, since this is one of the newest endpoints in the API and documentation is still filling in.
Getting started with Convex Lake's funding rate data
Convex Lake covers perpetual funding-rate data across Binance, Hyperliquid, Deribit, OKX, and Bybit under one schema, alongside orderbook, trades, and candle data for the same venues, plus Kalshi, Polymarket, Predict.fun, and Limitless on the prediction-market side. See the API docs for the current endpoint reference, or get in touch for access.

