Credentially · Authentication Profile

Credentially Authentication

Authentication

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

HealthcareCredentialingComplianceOnboardingWorkforceIdentity VerificationBackground ChecksNHSCompany
Methods: http Schemes: 1 OAuth flows: API key in:

Security Schemes

bearer-key http
scheme: bearer

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-18'
method: searched
source: openapi/credentially-gateway-openapi-original.json, openapi/credentially-webhook-openapi-original.json
docs: https://credentially.readme.io/reference/getting-started-with-your-api
summary:
  types:
  - http
  http_schemes:
  - bearer
notes: >-
  API keys are provisioned per organisation by a Credentially Customer Success Manager
  (support@credentially.io); pass as "Authorization: Bearer <API key>" (JWT). Keys grant
  access to all of the organisation's staff documents and data, so must be kept confidential.
  Webhook callbacks use a separate per-subscription Basic auth credential set by the subscriber.
schemes:
- name: bearer-key
  type: http
  scheme: bearer
  bearerFormat: JWT
  sources:
  - openapi/credentially-gateway-openapi-original.json
  - openapi/credentially-webhook-openapi-original.json