databento-python
The official Python client library for Databento.
Key features include:
- Fast, lightweight access to both live and historical data from multiple markets.
- Multiple schemas such as MBO, MBP, top of book, OHLCV, last sale, and more.
- Fully normalized, i.e. identical message schemas for both live and historical data, across multiple asset classes.
- Provides mappings between different symbology systems, including smart symbology for futures rollovers.
- Point-in-time instrument definitions, free of look-ahead bias and retroactive adjustments.
- Reads and stores market data in an extremely efficient file format using Databento Binary Encoding.
- Event-driven market replay, including at high-frequency order book granularity.
- Support for batch download of flat files.
- Support for pandas, CSV, and JSON.
Documentation
The best place to begin is with our Getting started guide.
You can find our full client API reference on the Historical Reference and Live Reference sections of our documentation. See also the Examples section for various tutorials and code samples.
Requirements
The library is fully compatible with distributions of Anaconda 2023.x and above.
The minimum dependencies as found in the pyproject.toml are also listed below:
- python >= 3.10
- aiohttp >= 3.8.3
- certifi >= 2026.10.19
- databento-dbn ~= 0.70.0
- numpy >= 1.23.5
- pandas >= 1.5.3
- pip-system-certs >= 4.0 (Windows only)
- pyarrow >= 13.0.0
- requests >= 2.27.0
- zstandard >= 0.21.0 (Python < 3.14 only)
Installation
To install the latest stable version of the package from PyPI:
pip install -U databento
Building from source
Building this project requires uv; no other Python tooling is needed, as uv provisions the interpreter and virtual environment for you.
git clone https://github.com/databento/databento-python.git
cd databento-python
scripts/build.sh
This creates a .venv in the project directory containing the dev dependency group and an
editable install of the package. From there:
scripts/test.sh # run the test suite
scripts/lint.sh # type check with mypy
uv run python # start a REPL in the environment
To produce a wheel and source distribution under dist/:
uv build
Usage
The library needs to be configured with an API key from your account.
Sign up for free and you will automatically
receive a set of API keys to start with. Each API key is a 32-character
string starting with db-, that can be found on the API Keys page of your Databento user portal.
A simple Databento application looks like this:
import databento as db
client = db.Historical('YOUR_API_KEY')
data = client.timeseries.get_range(
dataset='GLBX.MDP3',
symbols='ES.FUT',
stype_in='parent',
start='2022-06-10T14:30',
end='2022-06-10T14:40',
)
data.replay(callback=print) # market replay, with `print` as event handler
Replace YOUR_API_KEY with an actual API key, then run this program.
This uses .replay() to access the entire block of data
and dispatch each data event to an event handler. You can also use
.to_df() or .to_ndarray() to cast the data into a Pandas DataFrame or numpy ndarray:
df = data.to_df() # to DataFrame
array = data.to_ndarray() # to ndarray
Note that the API key was also passed as a parameter, which is
not recommended for production applications.
Instead, you can leave out this parameter to pass your API key via the DATABENTO_API_KEY environment variable:
import databento as db
# Pass as parameter
client = db.Historical('YOUR_API_KEY')
# Or, pass as `DATABENTO_API_KEY` environment variable
client = db.Historical()
License
Distributed under the Apache 2.0 License.
Metadata
Release files for databento 0.88.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| databento-0.88.0.tar.gz | 79.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| databento-0.88.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 175.8 kB
Release files / databento-0.88.0.tar.gz
| Download URL | databento-0.88.0.tar.gz |
|---|---|
| Size | 79.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4b92d35c00a33b43c87ce9b4d0f3876c63de9678b446202f29c562f0888258de
|
|
BLAKE2b-256 checksum How to use checksums |
8be8f7772dfa454cbd75ab6f1ebc88a9ba5de5f28959cad1c3178adfdd62aade
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.4 {"installer":{"name":"uv","version":"0.13.4","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / databento-0.88.0-py3-none-any.whl
| Download URL | databento-0.88.0-py3-none-any.whl |
|---|---|
| Size | 96.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fb20087f3e70fb15a3a630afe1acb9f3084937e9d6a9bd4a68910977095b2aa5
|
|
BLAKE2b-256 checksum How to use checksums |
463309792dc9af77f3567d1f52a47480c4c2c637bc8fcf8fe0e5a9733e8054bb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.4 {"installer":{"name":"uv","version":"0.13.4","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for databento 0.88.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.