Product roadmap

Historical and live market news.

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.

At present, there is no mechanism through which a customer can cancel a batch download request once that request has been submitted. This ticket is to track the release of a feature that would allow customers to cancel batch download requests if those requests have not yet been completed.

I’m evaluating Databento OPRA historical data for a research pipeline and would like to request a very small representative sample before purchasing access. Requested sample: Dataset: OPRA.PILLARSymbols/universe: SPX.OPT and SPXW.OPTSchema: cmbp-1Date: August 19, 2025Time window: 09:58–10:15 ETBroad/full parent-chain coverage, not ATM-onlyPlease preserve the original event and receive timestamps (ts_event and ts_recv), bid/ask, bid/ask sizes, actions/flags, publisher_id, instrument_id, and raw symbol mappings If possible, please also include for the same date: Date-valid instrument definitions for the included SPX/SPXW contractsStatistics records containing open interest (stat_type=9), including the actual morning publication records rather than a rewritten intraday snapshotAny sample cash-SPX index observations available for the same time window, ideally with original source/capture timestamps The purpose is only to verify technical compatibility before purchasing historical access. I need enough consecutive real data to test causal quote replay and exact 1-, 3-, 5-, and 10-minute state reconstruction. Even 15–20 minutes of real SPX/SPXW event data would be sufficient. Thank you.

Hello Databento Support, I recently noticed that I was charged(2026/08/31) for Databento, but I was not aware that this payment would be processed. I have not actually used the service, and there should be no meaningful usage or activity on my account. You should be able to confirm this by reviewing my account usage logs. Since the service has not been used, I would appreciate it if you could review the charge and issue a full refund. Please let me know if you need any additional information from me Thank you for your help. Best regards,

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.

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

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

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

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.

e.g. for S&P 500.

This serves as a master list of all other snapshot-like features on our roadmap. The scope of this ticket is potentially very large and ambiguous so we've broken this down into smaller tickets that you can follow separately. (Historical only) https://roadmap.databento.com/b/n0o5prm6/feature-ideas/add-historical-endpoint-for-latest-snapshot-of-any-schema. 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. The main benefit of this is for creating ticker tape or latest quote features, e.g. on a web app, after we start exposing intraday data over the historical/HTTP API (https://roadmap.databento.com/roadmap/expose-intraday-and-current-trading-session-historical-data-over-historical-http-api-and-clients). Likely endpoint names for this would be either timeseries.get_last or timeseries.get_snapshot. (Historical only) https://roadmap.databento.com/b/n0o5prm6/feature-ideas/provide-snapshots-as-of-specified-time-in-historical-api. Likely endpoint names for this would be either timeseries.get_last or timeseries.get_snapshot.(Live only) https://roadmap.databento.com/roadmap/add-periodic-mbo-book-snapshots-to-live-api. This allows a user to get the last published value of any given schema at a specified time. The main benefit of this would be to allow customers to subsample the data on server side and reduce cost, though the benefit is diminished with feature 5 on this list. Note that this would allow a user to emulate (1) relatively well since a user could potentially just pass in their current clock time or some time slightly ahead of the clock time. However, their underlying implementations would be different and (1) and (2) would likely be released separately. Likely endpoint names for this would be either timeseries.get_last_asof or `timeseries. (Live only) https://roadmap.databento.com/b/n0o5prm6/feature-ideas/allow-live-api-clients-to-request-for-mbo-snapshot-recovery. This provides resilience to gaps or data errors originating from Databento side. It could also be used for recovery of book state caused by client-side issues or disconnection, but would be less quick than feature (4) on this list.(Both historical and live) https://roadmap.databento.com/roadmap/fixed-interval-mbp-1-summaries-eg-1-minute-bbo-or-subsampled-bbo. The purpose of this is more to provide customers a convenience over fetching or subscribing MBP-1 and subsampling and forward filling the MBP-1 data themselves, which could be very expensive given the size of MBP-1 data and how the customer has no idea how far to look back for the "last" MBP-1 update prior to the 1 second or 1 minute refresh interval. Some of these are in development, hence the status of this entire ticket, however you should check on each individual one in case the specific feature you're looking for is still in Considering state.