Product roadmap

We've received some requests recently for Binance data. Please upvote if this is of interest. We're still determining whether this is worth the risk.

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.

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

Add a schema for calculated metrics like options greeks, e.g. implied volatility, delta, etc.

Trades in US equities that happen off-exchange are reported to one of three TRFs. NYSE provides information on trades reported to their TRF through their "NYSE Trades" feed. More information available here: https://www.nyse.com/markets/nyse/market-info

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.

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.

It might be possible to obtain CME trading session hours systematically in historical captures of the instrument definition messages, as embedded in tag-1682=MDSecurityTradingStatus. This ties to another proposed feature here.

futures and futures options OHLC, OI and volume from the LME

Currently, multi-leg products (spreads, strategies, combos) on CME/ICE are hard to use because our instrument definitions do not provide metadata about each underlying leg. The user has to infer the legs from the symbol. This is a form of lossy normalization, since CME/ICE does provide this in their security definitions in a repeating group, but our fixed instrument definition schemas are forced to discard this—they only provide the the instrument_id of the first underlying instrument through underlying_id. In the meantime, our recommendation to users is to either infer this from the symbol OR download the raw security/instrument definitions from the exchange (e.g. CME's is free on their FTP) OR get a pcap subscription from us. If you need historical secdefs copied from CME (since their FTP site only gives 1 day history), we can provide a courtesy backfill of these for a fixed cost.

Historical and live market news.

Support AWS S3 as an additional method of delivery, aside from HTTP and FTP.

This request is to make the API documentation available for download so it can be referenced offline.