Dext · Authentication Profile

Dext Authentication

Authentication

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

CompanyAccountingBookkeepingReceiptsExpense ManagementFinancial AutomationData HealthOCR
Methods: http Schemes: 1 OAuth flows: API key in:

Security Schemes

bearerAuth http
scheme: bearer

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-18'
method: searched
source: https://help.dext.com/en/articles/272702-data-health-insights-api
summary:
  types: [http]
  http_schemes: [bearer]
  api_key_in: []
  oauth2_flows: []
schemes:
- name: bearerAuth
  type: http
  scheme: bearer
  description: >-
    Practice-scoped API token sent as `Authorization: Bearer <token>`. Tokens
    are created and managed in the Dext web app under Practice settings > Data
    Health > API tokens. The token value is displayed once on creation in a
    modal and cannot be retrieved afterwards, so it must be stored securely.
  sources: [openapi/dext-data-health-openapi.yml]
notes: >-
  The public Data Health & Insights API uses static practice-scoped bearer
  tokens, not OAuth 2.0 (there is no documented authorization/token endpoint or
  scope surface for this API). Dext's product-level partner integrations with
  accounting platforms use their own OAuth flows, but those are not part of the
  documented public API.