Bitfinex
Bitfinex is planned for Phase 4, 2029, subject to a data agreement with Bitfinex. The plan covers spot pairs and perpetuals at every depth from L2 to L4.
What we plan to offer on Bitfinex.
Coverage of Bitfinex begins once a data agreement with Bitfinex is in place, and the final scope follows that agreement.
All spot pairs, including USD, USDT, EUR and GBP quotes.
USDT-margined perpetuals.
Not planned at launch. Margin funding (lending) is a separate product and outside this coverage.
Full-depth snapshots and deltas, merged across two regions by venue sequence number.
Every order add, modify and remove, plus fills, normalized to the shared event types.
L3 plus a participant id, if the data agreement with the venue includes participant-level data.
How we plan to capture Bitfinex.
Once a data agreement with Bitfinex is in place, we capture Bitfinex 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
- Not planned at launch
- 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
- Participant id
- Offered if the data agreement includes participant-level data
| Market | venue_symbol | symbol |
|---|---|---|
| Spot | tBTCUSD | BTC-USD |
| Spot | tBTCUST | BTC-USDT |
| Perpetual | tBTCF0:USTF0 | BTC-PERP |
Bitfinex uses UST for Tether and prefixes trading pairs with t. Both conventions stay in venue_symbol only. The full rules are in symbology.
- An order removal is normalized to a
cancelorfillevent inbook_l3. - Signed sizes (negative for asks) are replaced by
sideand a positivesize. - Fills appear in
tradeswith the venue trade id unchanged.
Where history starts.
The history available for Bitfinex depends on the agreement with Bitfinex. 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 | ● | Per agreement | fdc_capture | If the agreement includes participant-level data |
funding | ○ | · | · | Not planned at launch |
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 Bitfinex follows the agreement with Bitfinex. Gaps that survive the two-region merge are listed in the gaps table and never filled. See data quality.
Derived fields on Bitfinex.
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_...")
# L4 order events with participant ids
book = fdc.book(
venue="bitfinex",
symbol="BTC-USD",
depth="L4",
start="2029-06-04",
end="2029-06-04T01:00:00",
)
df = book.to_polars()curl -H "Authorization: Bearer fdc_live_..." \
"https://api.financedatacloud.com/v1/book/l4?venue=bitfinex&symbol=BTC-USD&start=2029-06-04T00:00:00Z&end=2029-06-04T00:05:00Z"{"op":"subscribe","channel":"book_l4","venue":"bitfinex","symbol":"BTC-USD"}aws s3 cp \
s3://fdc-archive/book_l4/venue=bitfinex/date=2029-06-04/BTC-USD.parquet .Compare with.
Centralized exchange. Planned, subject to a data agreement with Kraken.
View coverageCentralized exchange (spot). Planned, subject to a data agreement with Bitstamp.
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 Bitfinex to your pre-registration to register your interest.
EARLY ACCESS · PRE-SALE PRICINGPre-register for early access → DANIEL GARCIA · CEO & FOUNDERdaniel@financedatacloud.com →