Qubole · Authentication Profile

Qubole Authentication

Authentication

Qubole secures its APIs with apiKey across 1 declared security scheme, as derived from its OpenAPI definitions.

CompanyDataData LakeBig DataAnalyticsSparkPrestoHiveAirflowMachine LearningCloudData Engineering
Methods: apiKey Schemes: 1 OAuth flows: API key in: header

Security Schemes

QuboleApiToken apiKey
· in: header ()

Source

Authentication Profile

qubole-authentication.yml Raw ↑ 
generated: '2026-07-20'
method: searched
source: https://docs.qubole.com/en/latest/rest-api/ + github.com/qubole/qds-sdk-py (connection.py, qubole.py)
docs: https://docs.qubole.com/en/latest/rest-api/
summary:
  types:
  - apiKey
  api_key_in:
  - header
  oauth2_flows: []
schemes:
- name: QuboleApiToken
  type: apiKey
  in: header
  parameter_name: X-AUTH-TOKEN
  description: >-
    All Qubole Data Service (QDS) REST API calls are authenticated with a per-user
    Qubole API token sent in the X-AUTH-TOKEN request header. The token is retrieved
    from the Control Panel "My Accounts" tab and is commonly exported to the AUTH_TOKEN
    environment variable for use by the SDKs and the qds.py CLI. Confirmed in the
    official Python SDK (QuboleAuth.__call__ sets r.headers['X-AUTH-TOKEN']).
  sources:
  - https://docs.qubole.com/en/latest/rest-api/
  - https://github.com/qubole/qds-sdk-py/blob/master/qds_sdk/qubole.py
notes: >-
  Token-based (API key) auth only; no OAuth2/OIDC scope surface is published, so no
  scopes/ artifact is emitted. Access control is managed server-side via Qubole
  users, groups, roles, and object-level policies. HTTPS is enforced (all HTTP is
  redirected to HTTPS).