Product roadmap

Makes all of our historical and live features easier to integrate in JavaScript.

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)

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.

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

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.

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.

As published here, the recommended roll dates for equity futures do not correspond to the contract expiration. There is currently no continuous symbology which matches these published dates.

This would allow a user to get the latest published value of any given schema, within the boundaries allowed by licensing/entitlements/historical embargo window. Likely endpoint names for this would be either timeseries.get_last or timeseries.get_snapshot. The main benefit of this would be to support ticker tape-type use cases, especially when we've enabled entitlements to intraday data through the HTTP API. See also: List of other snapshot features on the roadmap

This would allow a user to get the latest published value of any given schema at a specified time in the past. Likely endpoint names for this would be either timeseries.get_last_asof or timeseries.get_snapshot_asof. The main benefit of this would be to reduce the cost for customers who wish to subsample the certain schemas like MBP-1, but also to look up some forms of static data (this will be more useful for corporate actions and events data). Currently, some customers are more cost-sensitive and rely on a large number of API requests to look back for the last value, e.g. of MBP-1 to get top of book, in some subsampling interval. Note however the benefit of this is diminished for price schemas when subsampled BBO and trades are released. See also: List of other snapshot features on the roadmap

We would like to connect with the sales rep to discuss our custom contract.

Currently, Databento provides top-of-book data for EDGO, XCBO, C2OX, BATO via the OPRA.PILLAR dataset. In the scope of this request, provide data for those venues as standalone datasets with market depth/mbo 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.

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).

To extend support to browser-based applications.