Hydrolix · Authentication Profile

Hydrolix Authentication

Authentication

Hydrolix secures its APIs with http across 2 declared security schemes, as derived from its OpenAPI definitions.

CompanyObservabilityLog AnalyticsData LakeStreamingClickHouseMonitoringTime Series

Methods: http Schemes: 2 OAuth flows: API key in:

Security Schemes

bearerAuth http

scheme: bearer

serviceAccount http

scheme: bearer

Source

Authentication Profile

generated: '2026-07-19'
method: searched
source: https://docs.hydrolix.io/latest/openapi/ + https://github.com/hydrolix/hdxcli
summary:
  types: [http]
  http_schemes: [bearer]
  credential_login: true
  service_accounts: true
  api_key_in: []
  oauth2_flows: []
notes: >-
  Hydrolix is deployed per-customer (BYOC on AWS/GCP/Kubernetes), so there is no single public
  API host — the base host is your own cluster hostname. The Config API authenticates with
  Hydrolix user credentials (username/password) exchanged for a bearer token, presented as an
  Authorization: Bearer header on subsequent requests. Service Accounts provide long-lived,
  non-interactive tokens for automation (used by hdxcli and the MCP server). No public OAuth2
  authorization-server or API-key scheme is documented.
schemes:
  - name: bearerAuth
    type: http
    scheme: bearer
    bearerFormat: JWT
    description: Bearer token obtained by logging in with Hydrolix credentials against the Config API.
    sources: [docs.hydrolix.io Config API reference]
  - name: serviceAccount
    type: http
    scheme: bearer
    description: Long-lived service-account token for automated / scripted access (hdxcli, MCP server).
    sources: [github.com/hydrolix/hdxcli]
docs: https://docs.hydrolix.io/latest/openapi/config-api/