Qwilt · Authentication Profile

Qwilt Authentication

Authentication

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

CompanyMediaCDNContent Delivery NetworkEdge ComputingVideo StreamingOpen CachingMedia DeliveryCertificatesInfrastructure
Methods: apiKey, http Schemes: 2 OAuth flows: API key in: header

Security Schemes

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

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-20'
method: derived
source: openapi/qwilt-certificate-manager-openapi.yml, openapi/qwilt-media-delivery-openapi.yml,
  openapi/qwilt-origin-allow-list-openapi.yml
summary:
  types:
  - apiKey
  - http
  api_key_in:
  - header
schemes:
- name: apiKeyAuth
  type: apiKey
  in: header
  parameter: Authorization
  description: 'API key sent as `Authorization: X-API-KEY <api-key>`.'
  sources:
  - openapi/qwilt-certificate-manager-openapi.yml
  - openapi/qwilt-media-delivery-openapi.yml
  - openapi/qwilt-origin-allow-list-openapi.yml
- name: bearerAuth
  type: http
  scheme: bearer
  description: Bearer token from the login service (cqloudLoginToken).
  sources:
  - openapi/qwilt-certificate-manager-openapi.yml
  - openapi/qwilt-media-delivery-openapi.yml
  - openapi/qwilt-origin-allow-list-openapi.yml