Crypto Futures Derivatives Data Scraper avatar

Crypto Futures Derivatives Data Scraper

Pricing

from $7.76 / 1,000 derivative metrics

Go to Apify Store
Crypto Futures Derivatives Data Scraper

Crypto Futures Derivatives Data Scraper

Collects structured open interest, funding-rate, and long/short-ratio data from the official public Binance, Bybit, and OKX futures APIs.

Pricing

from $7.76 / 1,000 derivative metrics

Rating

0.0

(0)

Developer

Vitalii Bondarev

Vitalii Bondarev

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

16 days ago

Last modified

Share

Crypto Futures Data Scraper — Open Interest, Funding Rate, Long/Short Ratio

Structured, machine-readable derivatives data for crypto futures — open interest, funding rate, and long/short account ratio — pulled directly from the official public REST APIs of Binance, Bybit, and OKX. No login, no API key, no browser rendering.

What it does

Coinglass-style dashboards aggregate their derivatives metrics from the exchanges themselves. This actor goes straight to the source: it calls Binance's, Bybit's, and OKX's own public futures endpoints (openInterest, openInterestHist, globalLongShortAccountRatio on Binance; open-interest and funding/history on Bybit; open-interest on OKX) and normalizes every response into one flat record schema. These are official, keyless, publicly documented exchange endpoints — not a reverse-engineered internal API and not a screenshot of a chart.

Input

  • Symbols (symbols) — array of linear futures symbols, e.g. BTCUSDT, ETHUSDT, SOLUSDT. Defaults to ["BTCUSDT", "ETHUSDT", "SOLUSDT"].
  • Exchanges (exchanges) — array select of binance, bybit, okx. Defaults to all three.
  • Maximum results (maxResults) — caps the total number of normalized records charged and pushed. Default 200.
  • Proxy configuration (proxyConfiguration) — Apify Proxy, RESIDENTIAL group, prefilled and required. Every exchange request is routed through it and rotates to a fresh session on retry, since Binance and Bybit both apply exchange-side, session-dependent geo-restrictions to a small share of requests.

Output fields

One flat record per metric per symbol per exchange:

FieldDescription
exchangebinance, bybit, or okx
symbolThe futures symbol as requested (Binance/Bybit format, e.g. BTCUSDT) or exchange-native form for OKX (e.g. BTC-USDT-SWAP)
metricopenInterest, openInterestValue, fundingRate, or longShortRatio
valueThe metric's numeric value
timestampExchange-reported timestamp for the data point (ms epoch)
scrapedAtISO 8601 UTC timestamp of when the actor fetched the record
platformcoinglass-style-aggregator (identifies the metric family; not a call to coinglass.com)

Binance requests can return up to three metrics per symbol (openInterest, openInterestValue, longShortRatio); Bybit returns openInterest and fundingRate; OKX returns openInterest and openInterestValue. Any exchange call that fails (a transient 403/451 or a malformed response) is retried once on a fresh proxy session and otherwise skipped without failing the run — you get partial results for that symbol/exchange pair rather than a hard error.

Pricing

Pay-per-result: derivative-metric-scraped, $0.008 per normalized record pushed. Nothing is charged for a symbol/exchange pair that returns no data. See the Store pricing tab for the current rate.

Notes

  • All three source APIs are official, publicly documented exchange endpoints — no authentication, no signed headers, and no scraping of coinglass.com itself.
  • Output is structured JSON with real numeric fields (exchange, metric, value, timestamp), not a screenshot or an image URL — every field is directly usable in a spreadsheet, dashboard, or trading script without any further parsing.
  • Multi-exchange in one run: query Binance, Bybit, and OKX together and get a single normalized schema back, instead of hitting three different API shapes yourself.
  • A small fraction of Binance/Bybit calls can be geo-restricted depending on the exit session; the actor retries automatically and reports only what it could confirm — it does not fabricate missing values.