KuCoin
KuCoin is planned for Phase 4, 2029, subject to a data agreement with KuCoin. The plan covers spot pairs and USDT- and coin-margined perpetuals, with L2 depth and L3 order events.
What we plan to offer on KuCoin.
Coverage of KuCoin begins once a data agreement with KuCoin is in place, and the final scope follows that agreement.
All spot pairs.
USDT-margined and coin-margined perpetuals.
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 KuCoin.
Once a data agreement with KuCoin is in place, we capture KuCoin 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
- Nanoseconds on trades; milliseconds on book updates 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 | BTC-USDT | BTC-USDT |
| USDT perpetual | XBTUSDTM | BTC-PERP |
| Inverse perpetual | XBTUSDM | BTC-USD-INV-PERP |
KuCoin futures symbols use XBT and an M suffix. Spot symbols already follow BASE-QUOTE. The full rules are in symbology.
- Quiet periods on thinly traded pairs are not gaps;
gapsonly records periods where capture itself was interrupted. - Delisted instruments stay in
instrumentswith adelisted_attime, and their history stays in the archive. - Nanosecond trade timestamps are stored without rounding in
ts_exchange.
Where history starts.
The history available for KuCoin depends on the agreement with KuCoin. 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 KuCoin follows the agreement with KuCoin. Gaps that survive the two-region merge are listed in the gaps table and never filled. See data quality.
Derived fields on KuCoin.
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="kucoin",
symbol="BTC-PERP",
depth="L3",
start="2029-06-04",
end="2029-06-04T01:00:00",
)
df = book.to_polars()
# funding at every settlement, then live
funding = fdc.funding(venue="kucoin", symbol="BTC-PERP",
start="2029-06-04", live=True)curl -H "Authorization: Bearer fdc_live_..." \
"https://api.financedatacloud.com/v1/book/l3?venue=kucoin&symbol=BTC-PERP&start=2029-06-04T00:00:00Z&end=2029-06-04T00:05:00Z"{"op":"subscribe","channel":"book_l3","venue":"kucoin","symbol":"BTC-PERP"}aws s3 cp \
s3://fdc-archive/book_l3/venue=kucoin/date=2029-06-04/BTC-PERP.parquet .Compare with.
Centralized exchange. Planned, subject to a data agreement with Bitget.
View coverageCentralized exchange. Planned, subject to a data agreement with Bybit.
View coverageCentralized exchange. Planned, subject to a data agreement with Bitfinex.
View coverageShape what ships next.
Pre-registered partners vote on which venues and datasets ship first. Add KuCoin to your pre-registration to register your interest.
EARLY ACCESS · PRE-SALE PRICINGPre-register for early access → DANIEL GARCIA · CEO & FOUNDERdaniel@financedatacloud.com →