Bitget
Bitget is planned for Phase 3, 2028, subject to a data agreement with Bitget. The plan covers spot, USDT-, USDC- and coin-margined perpetuals and delivery futures, with L2 depth and L3 order events.
What we plan to offer on Bitget.
Coverage of Bitget begins once a data agreement with Bitget is in place, and the final scope follows that agreement.
All spot pairs.
USDT-M, USDC-M and coin-margined perpetuals and delivery futures.
Funding at every settlement, with the rate used.
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 Bitget.
Once a data agreement with Bitget is in place, we capture Bitget 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
- 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 |
| USDT-M perpetual | BTCUSDT | BTC-PERP |
| USDC-M perpetual | BTCPERP | BTC-USDC-PERP |
| Coin-M perpetual | BTCUSD | BTC-USD-INV-PERP |
Bitget separates markets by product type, and the same symbol can appear in several. The product type is stored in instruments.venue_market. The full rules are in symbology.
- Delivery futures expiry times are stored in
instruments.expiry. - Coin-margined sizes are normalized to base-asset units, with
contract_sizeininstruments. - Funding settlements and the rate used land in
fundingon the same clock astrades.
Where history starts.
The history available for Bitget depends on the agreement with Bitget. 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 | |
extended | ● | Per agreement | computed from fdc_capture | |
instruments | ● | Per agreement | venue reference data | |
gaps | ● | Per agreement | fdc_capture |
History for Bitget follows the agreement with Bitget. Gaps that survive the two-region merge are listed in the gaps table and never filled. See data quality.
Derived fields on Bitget.
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="bitget",
symbol="BTC-PERP",
depth="L3",
start="2028-09-04",
end="2028-09-04T01:00:00",
)
df = book.to_polars()
# funding at every settlement, then live
funding = fdc.funding(venue="bitget", symbol="BTC-PERP",
start="2028-09-04", live=True)curl -H "Authorization: Bearer fdc_live_..." \
"https://api.financedatacloud.com/v1/book/l3?venue=bitget&symbol=BTC-PERP&start=2028-09-04T00:00:00Z&end=2028-09-04T00:05:00Z"{"op":"subscribe","channel":"book_l3","venue":"bitget","symbol":"BTC-PERP"}aws s3 cp \
s3://fdc-archive/book_l3/venue=bitget/date=2028-09-04/BTC-PERP.parquet .Compare with.
Centralized exchange. Planned, subject to a data agreement with Bybit.
View coverageCentralized exchange. Planned, subject to a data agreement with OKX.
View coverageCentralized exchange. Planned, subject to a data agreement with KuCoin.
View coverageShape what ships next.
Pre-registered partners vote on which venues and datasets ship first. Add Bitget to your pre-registration to register your interest.
EARLY ACCESS · PRE-SALE PRICINGPre-register for early access → DANIEL GARCIA · CEO & FOUNDERdaniel@financedatacloud.com →