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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Databento

Databento Users API

The users API from Databento — 28 operation(s) for users.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

Tagged areas include User. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 36 operations across 28 paths, and defines 25 schemas. It is described by OpenAPI 3.2.0, at version 0.167.1.

Requests are made against the base URL https://hist.databento.com/v0.

36 operations 28 paths 25 schemas 3 DELETE12 GET14 POST7 PUT

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 2

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

Paths & Operations 36

Across 28 paths, the API surfaces 36 operations — 3 DELETE, 12 GET, 14 POST, 7 PUT. Each is listed below with its method, path, parameters, and response codes.

users 36
GET
/v0/users/me
Read Current User
read_current_user_v0_users_me_get 1 param → 200401403404422
PUT
/v0/users/me/name
Update Current User Name
update_current_user_name_v0_users_me_name_put 1 param body → 200400401403404422
GET
/v0/users/me/email_update_intent
Get Email Update Intent
get_email_update_intent_v0_users_me_email_update_intent_get 1 param → 200401403404422
POST
/v0/users/me/email_update_intent
Create Email Update Intent
create_email_update_intent_v0_users_me_email_update_intent_post 1 param body → 200401403404409422
DELETE
/v0/users/me/email_update_intent
Delete Email Update Intent
delete_email_update_intent_v0_users_me_email_update_intent_delete 1 param → 200401403404422
GET
/v0/users/email_update
Get Email Update Intent Detail
get_email_update_intent_detail_v0_users_email_update_get 2 params → 200400422
PUT
/v0/users/email_update
Update User Email
update_user_email_v0_users_email_update_put 1 param body → 200422
PUT
/v0/users/me/password
Update Current User Password
update_current_user_password_v0_users_me_password_put 1 param body → 200401403404422
POST
/v0/users/me/keys
Create Current User Key
create_current_user_key_v0_users_me_keys_post 1 param body → 200401403400409422
GET
/v0/users/me/keys
Read Current User Keys
read_current_user_keys_v0_users_me_keys_get 1 param → 200401403404422
GET
/v0/users/me/keys/{name}
Read Current User Key By Name
read_current_user_key_by_name_v0_users_me_keys__name__get 1 param → 200401403404422
PUT
/v0/users/me/keys/{name}
Update Current User Key By Name
update_current_user_key_by_name_v0_users_me_keys__name__put 2 params body → 200401403404422
DELETE
/v0/users/me/keys/{name}
Delete Current User Key By Name
delete_current_user_key_by_name_v0_users_me_keys__name__delete 1 param → 200401403404422
PUT
/v0/users/me/keys/{name}/rotate
Rotate Current User Key By Name
rotate_current_user_key_by_name_v0_users_me_keys__name__rotate_put 2 params → 200401403404422
GET
/v0/users/me/settings
List Settings
list_settings_v0_users_me_settings_get 1 param → 200401403422
PUT
/v0/users/me/settings
Update Settings
update_settings_v0_users_me_settings_put 1 param body → 200401403422
GET
/v0/users/me/tutorials
List Tutorials
list_tutorials_v0_users_me_tutorials_get 1 param → 200401403422
POST
/v0/users/me/tutorials/{tutorial_id}/completed
Update Tutorial Completed
update_tutorial_completed_v0_users_me_tutorials__tutorial_id__completed_post 2 params → 200401403422
POST
/v0/users/me/billing
Billing Capture
billing_capture_v0_users_me_billing_post 1 param → 200401403422
POST
/v0/users/me/add_card
Add Payment Card
add_payment_card_v0_users_me_add_card_post 2 params → 200401403422
POST
/v0/users/me/update_default
Update Default
update_default_v0_users_me_update_default_post 1 param body → 200401403422
POST
/v0/users/me/edit_card
Edit Card
edit_card_v0_users_me_edit_card_post 1 param body → 200401403422
GET
/v0/users/me/list_cards
List Cards
list_cards_v0_users_me_list_cards_get 1 param → 200401403422
POST
/v0/users/me/delete_card
Delete Card
delete_card_v0_users_me_delete_card_post 1 param body → 200401403422
POST
/v0/users/me/cart
Save Cart
save_cart_v0_users_me_cart_post 1 param body → 200401403422
GET
/v0/users/me/cart
Read Cart
read_cart_v0_users_me_cart_get 1 param → 200401422
GET
/v0/users/me/notifications
Read Notifications
read_notifications_v0_users_me_notifications_get 1 param → 200401422
POST
/v0/users/me/notifications/read
Read And Update Notifications
read_and_update_notifications_v0_users_me_notifications_read_post 1 param → 200401422
POST
/v0/users/me/notifications/mark_as_read
Mark Notifications As Read
mark_notifications_as_read_v0_users_me_notifications_mark_as_read_post 1 param body → 200401422
GET
/v0/users/me/notifications/has_unread
Has Unread Notifications
has_unread_notifications_v0_users_me_notifications_has_unread_get 1 param → 200401422
POST
/v0/users/me/notifications/clear
Clear Notifications
clear_notifications_v0_users_me_notifications_clear_post 1 param → 200401422
GET
/v0/users/me/alerts
Get Alert Messages
get_alert_messages_v0_users_me_alerts_get 1 param → 200401422
PUT
/v0/users/me/alerts/dismissed/{msg_id}
Dismiss An Alert Message
dismiss_an_alert_message_v0_users_me_alerts_dismissed__msg_id__put 2 params → 200401403404422
DELETE
/v0/users/me/alerts/dismissed
Clear Dismissed State
clear_dismissed_state_v0_users_me_alerts_dismissed_delete 1 param → 200401422
POST
/v0/users/sales_inquiry
Create Sales Inquiry
create_sales_inquiry_v0_users_sales_inquiry_post 2 params body → 200422
POST
/v0/users/calendly_meeting_scheduled
Calendly Meeting Scheduled
calendly_meeting_scheduled_v0_users_calendly_meeting_scheduled_post 2 params → 200422

Schemas 25

The contract defines 25 schemas that model the data the API accepts and returns. The most detailed are CardEdit (9 properties), UserResponse (9 properties), SalesInquiryCreate (7 properties), Card (6 properties). Each schema is shown below with its type and property counts.

UserPasswordUpdate
object
2 properties 2 required
StripeSetupIntent
object
2 properties 2 required
UserEmailUpdateConfirm
object
1 property 1 required
CardEdit
object
9 properties 1 required
UserApiKeyUpdate
object
1 property 1 required
UserEmailUpdateIntent
object
5 properties 5 required
NotificationMsgIds
object
1 property 1 required
UserStatus
string
SalesInquiryCreate
object
7 properties
UserNameUpdate
object
1 property 1 required
TeamRole
string
Registration
string
UserSettingsView
object
6 properties 3 required
UserResponse
object
9 properties 6 required
UserApiKeyResponse
object
5 properties 5 required
UserCart
object
1 property 1 required
DetailResponse
object
1 property 1 required
UserSettingsUpdate
object
6 properties
UserApiKeyCreate
object
1 property 1 required
PaymentMethod
object
1 property 1 required
HTTPValidationError
object
1 property
Card
object
6 properties 6 required
EmailUpdateStatus
string
ValidationError
object
3 properties 3 required
UserUpdateNewEmail
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

databento-users-api-openapi.yml Raw ↑

Other APIs Databento publishes across the network.

Databento Historical Timeseries API
AE Profile APIs.io
Databento Metadata API
AE Profile APIs.io
Databento Symbology API
AE Profile APIs.io
Databento Batch API
AE Profile APIs.io
Databento Live Streaming API
AE Profile APIs.io
Databento Reference API
AE Profile APIs.io
Databento Adjustment Factors API
AE Profile APIs.io
Databento Analytics API
AE Profile APIs.io
Databento Auth API
AE Profile APIs.io
Databento Billing API
AE Profile APIs.io
Databento Corporate Actions API
AE Profile APIs.io
Databento Databento OpenAPI Specification API
AE Profile APIs.io
#User
← Back to D APIs
API Details
ID
databento:databento-users-api
Base URL
https://hist.databento.com/v0
Docs
https://databento.com/docs/api-reference-historical/timeseries/timeseries-get-range
Provider
Databento
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=databento-users-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/databento-users-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Databento Users 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.