Breathe Battery Technologies · Authentication Profile

Breathe Battery Technologies Authentication

Authentication

Breathe Battery Technologies secures its APIs with bearer-token across 1 declared security scheme, as derived from its OpenAPI definitions.

CompanyBatteryBattery SimulationElectric VehiclesEnergy StorageCell DesignPhysics-Based ModelingAutomotiveDeep TechDeveloper Tools

Methods: bearer-token Schemes: 1 OAuth flows: API key in:

Security Schemes

BearerToken http

scheme: bearer

Source

Authentication Profile

generated: '2026-07-18'
method: searched
source: https://docs.breathebatteries.com/breathe-simulate-documentation/api_breathe_design_model/
docs: https://docs.breathebatteries.com/
summary:
  types:
  - bearer-token
  api_key_in: []
  oauth2_flows: []
  notes: >-
    Access is mediated by the first-party Python client (breathe-simulate / breathe-design). The
    client authenticates against the Breathe cloud service using a token that it obtains and
    refreshes automatically (an ensure_logged_in() step that "checks if a valid token is
    available and refreshes it if necessary"). The service base URL is provisioned per account
    via a BD_* environment variable and is not published in the public documentation. No public
    OpenAPI specification, OAuth authorization/token endpoints, or API-key header scheme are
    documented on the public surface.
schemes:
- name: BearerToken
  type: http
  scheme: bearer
  sources:
  - https://docs.breathebatteries.com/breathe-simulate-documentation/api_breathe_design_model/
  description: >-
    Token-based authentication handled by the SDK's login/refresh flow; token acquisition is not
    documented as a public endpoint.