Doppel · Authentication Profile

Doppel Authentication

Authentication

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

CompanySecurityCybersecurityDigital Risk ProtectionSocial Engineering DefenseBrand ProtectionAnti-PhishingThreat IntelligenceHuman Risk ManagementTakedowns
Methods: apiKey Schemes: 2 OAuth flows: API key in: header

Security Schemes

api_key apiKey
· in: header (x-api-key)
user_api_key apiKey
· in: header (x-user-api-key)

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-18'
method: searched
source: openapi/doppel-openapi-original.yml
docs: https://doppel.readme.io/docs/authentication
summary:
  types:
  - apiKey
  api_key_in:
  - header
  notes: >-
    Doppel V1 authenticates with static API keys passed as request headers. User-specific
    (recommended): send both x-api-key (org key) and x-user-api-key (per-user, self-service,
    self-rotatable, RBAC-scoped). Organization-wide: send x-api-key only. No OAuth2/OIDC surface.
schemes:
- name: api_key
  type: apiKey
  in: header
  parameter: x-api-key
  description: API key from Doppel Vision API settings. Required for gateway authentication
    and quota.
  sources:
  - openapi/doppel-openapi-original.yml
- name: user_api_key
  type: apiKey
  in: header
  parameter: x-user-api-key
  description: User API key from Doppel Vision API settings. Required together with x-api-key
    for authenticated requests.
  sources:
  - openapi/doppel-openapi-original.yml