Crypto Futures Derivatives Data Scraper

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:

Field	Description
exchange	binance, bybit, or okx
symbol	The futures symbol as requested (Binance/Bybit format, e.g. BTCUSDT) or exchange-native form for OKX (e.g. BTC-USDT-SWAP)
metric	openInterest, openInterestValue, fundingRate, or longShortRatio
value	The metric's numeric value
timestamp	Exchange-reported timestamp for the data point (ms epoch)
scrapedAt	ISO 8601 UTC timestamp of when the actor fetched the record
platform	coinglass-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.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.