Product roadmap

This feature would allow the user to request trading calendar information (such as trading session start/end times) via our API. This is especially useful when considering trading sessions that can span multiple UTC dates (and hence the possibility of having multiple trading sessions within a single day). Keywords: Market calendar, trading holidays.

All orders plus last look quotes from 35 major banks and non-bank LPs, on one of the largest FX venues.

From EEX CEF Core feed EEX EOBI feed. This will include order-by-order data as well as less granular formats, such daily settlements, definitions, etc.

Only regular trading hours are supported currently.

B3: Brazil Equities and Futures MBO data. Keywords for search purposes: Brasil Bolsa Balcão S.A., Brazilian Mercantile and Futures Exchange (BM&F), BMF, Bovespa (São Paulo Stock Exchange), Cetip (Central of Custody and Financial Settlement of Securities for the organized OTC market).

Macroeconomic data releases, such as: Jobs Inflation, e.g. CPI FOMC

test

Currently, indices are indirectly supported through tradable index instruments on CME futures, ETFs, etc. and we don't provide the index values (non-tradable) themselves. This may be sourced from a feed like the Cboe Global Indices Feed or NYSE Global Index Feed.

Full depth of book feed for Cboe Futures Exchange (CFE). CFE contains volatility futures and corporate bond index futures, such as VIX futures (VX, VXM).

Data for Eurex, including all schemas (MBO, MBP, ohlcv, etc.).

Currently, equities is supported via individual prop feeds of each venue. While NASDAQ is sufficient for getting NBBO for most of the time, some users prefer something that will be more in line with actual NBBO from SIPs. This feature request tracks 3 possible modes of consolidation for both historical and live data: Databento server-side consolidation of multiple proprietary feeds Consolidated data from proprietary feed like Nasdaq Basic in lieu of SIP Consolidated data from CTA/UTP SIPs We plan on implementing 1-2 of these three options.

To extend support to browser-based applications.

e.g. for S&P 500.

Support Parquet as a form of encoding, aside from dbn, CSV and JSON.

This client library makes all our historical and live features easier to integrate in C# on Windows, Linux, and Mac OS. C# is currently already supported through our HTTP API and Raw TCP protocol, which are both language-agnostic.