Incognia · Authentication Profile

Incognia Authentication

Authentication

Incognia secures its APIs with http and oauth2 across 3 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the clientCredentials flow(s).

CompanyCybersecurityFraud PreventionDevice FingerprintingLocation IdentityIdentity VerificationRisk AssessmentAuthenticationFintechAnti-Fraud
Methods: http, oauth2 Schemes: 3 OAuth flows: clientCredentials API key in:

Security Schemes

basicAuth http
scheme: basic
bearerAuth http
scheme: bearer
oauth2 oauth2
· flows: clientCredentials

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-19'
method: derived
source: openapi/incognia-openapi-original.yml
summary:
  types:
  - http
  - oauth2
  oauth2_flows:
  - clientCredentials
schemes:
- name: basicAuth
  type: http
  scheme: basic
  description: client_id and client_secret sent as HTTP Basic credentials to the token endpoint.
  sources:
  - openapi/incognia-openapi-original.yml
- name: bearerAuth
  type: http
  scheme: bearer
  bearerFormat: JWT
  description: OAuth 2.0 bearer access token obtained from POST /v2/token.
  sources:
  - openapi/incognia-openapi-original.yml
- name: oauth2
  type: oauth2
  flows:
  - flow: clientCredentials
    tokenUrl: https://api.incognia.com/api/v2/token
    scopes: 0
  description: OAuth 2.0 client-credentials grant. No scopes are defined; access is scoped by
    the credential's tenant.
  sources:
  - openapi/incognia-openapi-original.yml