Product roadmap

Submit dataset requests and feature ideas here. For bug reports, use our chat support or issues tracker instead.

Trending
  1. Fixed-interval MBP-1 summaries (e.g. "1 minute BBO" or "subsampled BBO")

    For options, including in the CME and OPRA datasets, the existing mbp-1 schema can have significant record volume despite the instruments being extremely illiquid. In practice, there are several orders of magnitude more mbp-1 records than trades, which is unwieldy to work with. Many services offer BBO summaries at a fixed interval, such as 1 or 10 minutes. This would be similar to the ohlcv-1m schema, but include BBO information that is present in mbp-1 and tbbo instead of only containing trades. This would be a new schema (or set of schemas). What kind of information would you like to see in the MBP-1 summary message? Edit: Adding a few keywords here to facilitate searchβ€”subsampled BBO, subsampled MBP-1, MBP-1 snapshots.

    Zach Banks
    #Datasets πŸ“Ά

    5

  2. CFE Book Depth

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

    Zach Banks
    #Datasets πŸ“Ά

    0

  3. Calculated options greeks schema

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

    Carter Green
    #APIs πŸ”—

    6

  4. Expose metadata of every underlying leg in multi-leg futures and options

    Currently, multi-leg products 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.

    Tessa Hollinger
    #Datasets πŸ“Ά#APIs πŸ”—

    1

  5. FX swaps data

    I would be nice to have swaps and swaptions data for main currencies but also for EMEA countries.

    Jose M
    #Datasets πŸ“Ά#APIs πŸ”—

    1

  6. CME options settlement data

    Everyday the CME publishes settlements on all listed options. Included are BBOs/OI/Volume/ etc

    Nate K
    #Datasets πŸ“Ά

    1

  7. Historical open interest on expired options contracts

    I am looking for historical data, specifically for open interest on expired options contracts. Here is an example of the query I would want to do. I have the options ticker O:AAPL240510C00190000 and I would want to know the open interest on that ticker for 2024-05-09? Also I am using python code. Thank you for your help with this!

    Christopher B

    1

  8. Better API key security on frontend

    Currently, there are several areas where security around our API keys could be hardened. This ticket tracks the scope of 2 specific improvements: The doc site embeds your production API key in all of the examples when you're logged in. (A) Users who are inexperienced with API integrations may not have read the Securing your API keys guide and could quite easily make the mistake of copying and pasting their keys somewhere insecure, e.g. source control, Databento Slack community. (B) Users who are screensharing could accidentally reveal their API keys.The portal API keys page doesn't hide the API keys, so someone who's screensharing could easily reveal their API keys there as well.

    Tessa Hollinger
    #Portal πŸ–₯

    0

  9. Corporate actions data

    Dividends, stock splits, mergers, ticker changes, adjusted EOD historical prices.

    Carter Green
    #Datasets πŸ“Ά

    4

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

    Renan Gemignani
    #APIs πŸ”—

    1

  11. 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 Hollinger
    #Datasets πŸ“Ά

    3

  12. 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 Hollinger
    #Datasets πŸ“Ά#APIs πŸ”—

    7

  13. Official C# client library

    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.

    Tessa Hollinger
    #APIs πŸ”—

    4

  14. Provide snapshots for historical and live data

    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.

    Tessa Hollinger
    #APIs πŸ”—

    7

  15. Parquet encoding

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

    Tessa Hollinger
    #APIs πŸ”—#Portal πŸ–₯

    11