Bybit
Bybit is planned for Phase 2, 2027, subject to a data agreement with Bybit. The plan covers spot, linear and inverse perpetuals, dated futures and options, with L2 depth and L3 order events.
What we plan to offer on Bybit.
Coverage of Bybit begins once a data agreement with Bybit is in place, and the final scope follows that agreement.
All spot pairs listed on the venue.
Linear USDT and USDC perpetuals, inverse perpetuals, dated futures and USDC options.
Funding at every settlement, with each change of interval recorded.
Full-depth snapshots and deltas, merged across two regions by venue sequence number.
Order events normalized to add, modify, cancel and fill.
Offered if the venue's data agreement includes participant-level data.
How we plan to capture Bybit.
Once a data agreement with Bybit is in place, we capture Bybit independently from two regions and merge the two streams by venue sequence number, as we do for every venue. Production capture starts at least 90 days before early access, so depth history covers three months or more on day one.
- Venue type
- Centralized exchange
- Funding interval
- 8 hours; 4 hours on some contracts
- Integrity
- Venue sequence numbers, and book checksums where the feed includes them, verified at capture
- Snapshots
- A full-depth book snapshot at the top of every UTC hour (the 00:00 snapshot opens each daily file), plus the venue's own snapshots on reconnect, flagged with
is_snapshotandsnapshot_reason - Timestamps
- Milliseconds in
ts_exchange.ts_captureis int64 nanoseconds from a PTP-disciplined clock. - Regions
- Two independent regions, assigned once the data agreement is in place
| Market | venue_symbol | symbol |
|---|---|---|
| Spot | BTCUSDT | BTC-USDT |
| Linear perpetual | BTCUSDT | BTC-PERP |
| USDC perpetual | BTCPERP | BTC-USDC-PERP |
| Inverse perpetual | BTCUSD | BTC-USD-INV-PERP |
| Dated future | BTC-25JUN27 | BTC-25JUN27 |
| Option | BTC-25JUN27-90000-C | BTC-25JUN27-90000-C |
The native symbol BTCPERP is the USDC perpetual and maps to BTC-USDC-PERP. The full mapping is stored in instruments. The full rules are in symbology.
- Snapshots sent mid-stream are kept and marked
is_snapshot = truewithsnapshot_reason = "venue"inbook_l2. - Inverse contract sizes are normalized to base-asset units; the native value can be recovered with
contract_sizefrominstruments. - Liquidations land in
liquidationson the same clock astrades.
Where history starts.
The history available for Bybit depends on the agreement with Bybit. Data we capture ourselves starts on the first day of production capture, which begins once that agreement is in place.
| Table | Offered | History from | source | Note |
|---|---|---|---|---|
trades | ● | Per agreement | fdc_capture | |
candles | ● | Per agreement | fdc_capture | |
quotes | ● | Per agreement | fdc_capture | |
book_l2 | ● | Per agreement | fdc_capture | |
book_l3 | ● | Per agreement | fdc_capture | |
book_l4 | ○ | · | · | Offered if the agreement includes participant-level data |
funding | ● | Per agreement | fdc_capture | |
open_interest | ● | Per agreement | fdc_capture | |
liquidations | ● | Per agreement | fdc_capture | |
mark_index | ● | Per agreement | fdc_capture | |
options_chain | ● | Per agreement | fdc_capture | If the agreement includes options data |
extended | ● | Per agreement | computed from fdc_capture | |
instruments | ● | Per agreement | venue reference data | |
gaps | ● | Per agreement | fdc_capture |
History for Bybit follows the agreement with Bybit. Gaps that survive the two-region merge are listed in the gaps table and never filled. See data quality.
Derived fields on Bybit.
Extended fields are computed on ts_capture and published on a 100 ms grid. A field is available on a venue when its source data is.
Query it.
The same calls work on every venue; only venue and symbol change. Endpoints go live with Phase 1, and the v1 spec is a draft until then.
from fdc import Client
fdc = Client(api_key="fdc_live_...")
# L3 order events
book = fdc.book(
venue="bybit",
symbol="BTC-PERP",
depth="L3",
start="2027-11-08",
end="2027-11-08T01:00:00",
)
df = book.to_polars()
# funding at every settlement, then live
funding = fdc.funding(venue="bybit", symbol="BTC-PERP",
start="2027-11-08", live=True)curl -H "Authorization: Bearer fdc_live_..." \
"https://api.financedatacloud.com/v1/book/l3?venue=bybit&symbol=BTC-PERP&start=2027-11-08T00:00:00Z&end=2027-11-08T00:05:00Z"{"op":"subscribe","channel":"book_l3","venue":"bybit","symbol":"BTC-PERP"}aws s3 cp \
s3://fdc-archive/book_l3/venue=bybit/date=2027-11-08/BTC-PERP.parquet .Compare with.
Centralized exchange. Planned, subject to a data agreement with Binance.
View coverageCentralized exchange. Planned, subject to a data agreement with OKX.
View coverageCentralized exchange. Planned, subject to a data agreement with Bitget.
View coverageShape what ships next.
Pre-registered partners vote on which venues and datasets ship first. Add Bybit to your pre-registration to register your interest.
EARLY ACCESS · PRE-SALE PRICINGPre-register for early access → DANIEL GARCIA · CEO & FOUNDERdaniel@financedatacloud.com →