Product roadmap

Only regular trading hours are supported currently.

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

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

Via streamlined SBE.

Australian Stocks with ASX and CBOE trades

The Eurex dataset (XEUR.EOBI) has availability from 2025-03-10. This request is to backfill this dataset with more history. A source of this history has not been identified, we will update this ticket when/if it is accepted with details.

Hi, I was charged $471.63 dollars but I not longer had subscription. My previous subscription was already cancelled few weeks ago. I would like to request the reimbursment . Thank you Andres Escobar 9499661546

About 6 months ago i ordered access for 6 months of pcap data during 2025 for CME for account AWS account 891612553438. I need access immediately my email is albi@taconictrading.com and my name is Albi Tocilla.

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.

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.

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.

Historical and live market news.