How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Databento Metadata API

Discovery and cost-estimation endpoints for the historical catalog. List publishers, datasets, schemas, and fields; look up per-dataset date ranges and data-quality conditions; and pre-compute the record count, billable size, and dollar cost of a query before you run it. Essential for planning research and controlling spend on financial and reference data.

Databento Metadata API is one of 24 APIs that Databento publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Metadata, Reference Data, Market Data, Datasets, and Financial Data. The published artifact set on APIs.io includes API documentation, an API reference, and an OpenAPI specification.

This API exposes 23 operations across 20 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://hist.databento.com/v0.

23 operations 20 paths 6 schemas 20 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://hist.databento.com/v0
Authentication
HTTP Basic, OAuth 2.0, HTTP Basic
Resource Areas
1

Authentication & Security 3

Databento Metadata API declares 3 security schemes for authenticating requests. It accepts HTTP basic authentication (apiKeyBasicAuth). It supports OAuth 2.0 (OAuth2PasswordBearerWithCookie) using the password flow. It accepts HTTP basic authentication (HTTPBasic).

  • apiKeyBasicAuth — HTTP Basic authentication. Supply your Databento API key (prefixed with db-) as the username and leave the password empty.

Paths & Operations 23

Across 20 paths, the API surfaces 23 operations — 20 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Metadata 23

Catalog discovery, dataset ranges and conditions, and cost estimation.

GET
/metadata.list_publishers
List publishers
listPublishers → 200401
GET
/metadata.list_datasets
List datasets
listDatasets 2 params → 200401
GET
/metadata.list_schemas
List schemas
listSchemas 1 param → 200401
GET
/metadata.list_fields
List fields
listFields 2 params → 200401
GET
/metadata.list_unit_prices
List unit prices
listUnitPrices 1 param → 200401
GET
/metadata.get_dataset_condition
Get dataset condition
getDatasetCondition 3 params → 200401
GET
/metadata.get_dataset_range
Get dataset range
getDatasetRange 1 param → 200401
GET
/metadata.get_record_count
Get record count
getRecordCount 5 params → 200401
GET
/metadata.get_billable_size
Get billable size
getBillableSize 5 params → 200401
GET
/metadata.get_cost
Get cost
getCost 6 params → 200401
GET
/v0/metadata.list_publishers
List Publishers
list_publishers_v0_metadata_list_publishers_get 1 param → 200422
GET
/v0/metadata.list_datasets
List Available Datasets
list_available_datasets_v0_metadata_list_datasets_get 3 params → 200422
GET
/v0/metadata.list_schemas
List Available Schemas
list_available_schemas_v0_metadata_list_schemas_get 2 params → 200422
GET
/v0/metadata.list_fields
List Available Fields
list_available_fields_v0_metadata_list_fields_get 3 params → 200422
GET
/v0/metadata.list_unit_prices
List Unit Prices
list_unit_prices_v0_metadata_list_unit_prices_get 2 params → 200400404422429
GET
/v0/metadata.get_dataset_range
Get Dataset Range
get_dataset_range_v0_metadata_get_dataset_range_get 2 params → 200400404422429
GET
/v0/metadata.get_dataset_condition
Get Dataset Condition
get_dataset_condition_v0_metadata_get_dataset_condition_get 4 params → 200400404422429
POST
/v0/metadata.get_record_count
Post Get Record Count
post_get_record_count_v0_metadata_get_record_count_post 1 param body → 200400404422429
GET
/v0/metadata.get_record_count
Get Record Count
get_record_count_v0_metadata_get_record_count_get 9 params → 200400404422429
POST
/v0/metadata.get_billable_size
Post Get Billable Size
post_get_billable_size_v0_metadata_get_billable_size_post 1 param body → 200400404422429
GET
/v0/metadata.get_billable_size
Get Billable Size
get_billable_size_v0_metadata_get_billable_size_get 9 params → 200400404422429
POST
/v0/metadata.get_cost
Post Get Cost
post_get_cost_v0_metadata_get_cost_post 1 param body → 200400404422429
GET
/v0/metadata.get_cost
Get Cost
get_cost_v0_metadata_get_cost_get 10 params → 200400404422429

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are Body_post_get_cost_v0_metadata_get_cost_post (9 properties), Body_post_get_record_count_v0_metadata_get_record_count_post (8 properties), Body_post_get_billable_size_v0_metadata_get_billable_size_post (8 properties), ValidationError (3 properties). Each schema is shown below with its type and property counts.

Error
object
2 properties
Body_post_get_cost_v0_metadata_get_cost_post
object
9 properties 2 required
Body_post_get_billable_size_v0_metadata_get_billable_size_post
object
8 properties 2 required
Body_post_get_record_count_v0_metadata_get_record_count_post
object
8 properties 2 required
HTTPValidationError
object
1 property
ValidationError
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

databento-metadata-api-openapi.yml Raw ↑

Other APIs Databento publishes across the network.

Databento Symbology API
Databento Batch API
Databento Live Streaming API
Databento Reference API
Databento Adjustment Factors API
Databento Analytics API
Databento Auth API
Databento Billing API
Databento Corporate Actions API
Databento OpenAPI Specification API
Databento Dataset API
Databento Display API
Where this information came from

This is an independent, third-party profile of Databento Metadata API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.