Qovery · Authentication Profile

Qovery Authentication

Authentication

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

Cloud DeploymentDeveloper ExperienceInternal Developer Platform
Methods: apiKey, http Schemes: 2 OAuth flows: API key in: header

Security Schemes

bearerAuth http
scheme: bearer
ApiKeyAuth apiKey
· in: header (Authorization)

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-11'
method: derived
source: openapi/qovery-openapi.yaml
summary:
  types:
  - apiKey
  - http
  api_key_in:
  - header
schemes:
- name: bearerAuth
  type: http
  scheme: bearer
  bearerFormat: JWT
  description: 'JWT tokens should be used with OIDC account (human to machine). JWT tokens used
    by the Qovery console to communicate with the API have a TTL. Curl Example '' curl https://console.qovery.com/organization
    -H "Authorization: Bearer $qovery_token" '''
  sources:
  - openapi/qovery-openapi.yaml
- name: ApiKeyAuth
  type: apiKey
  in: header
  parameter: Authorization
  description: 'Token API are generated by Qovery to manage machine to machine interaction and
    do not have a TTL. Curl Example '' curl https://console.qovery.com/organization -H "Authorization:
    Token $qovery_token" '''
  sources:
  - openapi/qovery-openapi.yaml