AU10TIX · Authentication Profile

Au10Tix Authentication

Authentication

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

Identity VerificationDocument AuthenticationKYCBiometricsFraud Detection
Methods: apiKey, http Schemes: 2 OAuth flows: API key in: header

Security Schemes

bearerAuth http
scheme: bearer
clientCertificate apiKey
· in: header (X-Client-Certificate)

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-11'
method: derived
source: openapi/au10tix-openapi.yml
summary:
  types:
  - apiKey
  - http
  api_key_in:
  - header
schemes:
- name: bearerAuth
  type: http
  scheme: bearer
  bearerFormat: JWT
  description: OAuth2 access token (JWT) presented as a Bearer token in the Authorization header
    on each request to the current BOS REST API.
  sources:
  - openapi/au10tix-openapi.yml
- name: clientCertificate
  type: apiKey
  in: header
  parameter: X-Client-Certificate
  description: Legacy BOS integrations are secured by certificate-based authentication (mutual
    TLS); AU10TIX issues a unique client certificate to each calling party. Represented here
    as a security scheme placeholder because mutual TLS is configured at the transport layer
    rather than in a request header.
  sources:
  - openapi/au10tix-openapi.yml