Product roadmap
Submit requestSubmit dataset requests and feature ideas here. For bug reports, use our chat support or issues tracker instead.
Calculated options greeks schema
Add a schema for calculated metrics like options greeks, e.g. implied volatility, delta, etc.
Carter Green15
Support for Global Trading Hours (GTH) on OPRA US options data
Only regular trading hours are supported currently.
Carter Green7
Trading calendar information
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.
Renan Gemignani (Databento)8
Improved performance/latency optimization best practices guide
The current guide (https://databento.com/docs/architecture/performance-optimization) was written pre-launch and now best practices have drifted a bit.
Tessa Hollinger1
Parquet encoding
Support Parquet as a form of encoding, aside from dbn, CSV and JSON.
Tessa Hollinger12
Index component weightings
e.g. for S&P 500.
Tessa Hollinger5
London Metal Exchange (LME)
Futures and options on futures from LME. This will be captured at LON2 colo and include both L2 (for implied pricing) and L3 feed (order-by-order). Lower granularities like OHLC, OI, settlement volume, etc. will be included as well
Felix E1
Include OPRA trade conditions
It would be helpful if OPRA trade conditions were included in the normalized schemas. This is useful information that's currently lost during normalization. Also include the "message type" of each last sale message. Similar to: https://roadmap.databento.com/roadmap/us-equity-trade-condition-codes
Carter Green8
Smart symbology for options
At the moment, options data users have to rely on fetching the definition schema and filtering for symbols that they're interested in using fields like expiration, asset, underlying_product, instrument_class, group, and strike_price. It would be convenient to fetch the options or options chains with particular conditions on expiration and strike price without going through the definition schema. This would be similar to smart symbology for futures. Note that even after this feature is released, we still recommend users to use definition as it gives more control and transparency over the symbology resolution.
Tessa Hollinger8
cuanto e smi saldo
Luis David P0
Real-time and historical index data
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.
Tessa Hollinger33
Consolidated US equities data
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.
Tessa Hollinger17
WebSocket API for live data
To extend support to browser-based applications.
Tessa Hollinger8
Cboe FX ITCH (forex, foreign exchange)
All orders plus last look quotes from 35 major banks and non-bank LPs, on one of the largest FX venues.
Tessa Hollinger18
Binance data (cryptocurrency spot, futures, options)
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.
Christina Qi6