Qomplement · Authentication Profile

Qomplement Authentication

Authentication

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

CompanyDocument ExtractionOCRStructured DataArtificial IntelligenceForms AutomationPDFSupply ChainDeveloper APIY Combinator
Methods: apiKey Schemes: 1 OAuth flows: API key in: header

Security Schemes

bearerApiKey apiKey
· in: header (Authorization)

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-20'
method: searched
source: openapi/qomplement-openapi-original.json
docs: https://docs.qomplement.com/api/authentication
summary:
  types: [apiKey]
  api_key_in: [header]
  scheme: bearer
  oauth2_flows: []
  note: >-
    The published OpenAPI declares no securitySchemes; authentication is documented
    only in the developer docs. All API requests require an API key passed as a
    Bearer token in the Authorization header.
schemes:
- name: bearerApiKey
  type: apiKey
  in: header
  parameter: Authorization
  format: "Bearer <api_key>"
  key_prefix: sd_
  key_format: sd_ followed by 48 hexadecimal characters
  issued_from: https://developers.qomplement.com
  sources: [https://docs.qomplement.com/api/authentication]
unauthorized:
  statuses: [401, 403]
  message: Could not validate credentials
notes:
  - No sandbox / separate test vs live key prefix is documented.
  - Keys are shown only once at creation and carry per-minute and monthly limits.