Certifaction · Authentication Profile

Certifaction Authentication

Authentication

Certifaction secures its APIs with apiKey and oauth2 across 2 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the oidc-external flow(s).

CompanyAi Enterprise SoftwareElectronic SignatureDigital SignatureDocument SigningQualified Electronic SignatureeIDASPrivacyComplianceIdentity VerificationSwitzerland
Methods: apiKey, oauth2 Schemes: 2 OAuth flows: oidc-external API key in: header

Security Schemes

api_key apiKey
· in: header (Authorization)
access_token oauth2
scheme: bearer · in: header (Authorization)

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-18'
method: searched
source: https://developers.certifaction.com/en/references/authentication
docs: https://developers.certifaction.com/en/references/authentication
summary:
  types:
  - apiKey
  - oauth2
  api_key_in:
  - header
  oauth2_flows:
  - oidc-external
schemes:
- name: api_key
  type: apiKey
  in: header
  parameter: Authorization
  usage: Server-side integration. API keys are managed from the Certifaction web application.
  sources:
  - openapi/certifaction-admin-api-openapi.yml
  - openapi/certifaction-local-api-openapi.yml
- name: access_token
  type: oauth2
  scheme: bearer
  in: header
  parameter: Authorization
  usage: >-
    Access tokens issued by the customer or by an external OIDC provider that
    Certifaction has registered. Passed in the Authorization header (CLI `-t/--token`).
  sources:
  - https://developers.certifaction.com/en/references/authentication
notes: >-
  The OpenAPI declares only the api_key scheme; the documented access-token/OIDC
  option is added from the authentication reference page.