Dataddo Authentication

generated: '2026-10-20'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://docs.dataddo.com/headless/docs/creating-an-authorizer.md
sources:
- https://docs.dataddo.com/headless/docs/creating-an-authorizer.md
- https://docs.dataddo.com/headless/docs/authorizing-non-oauth-20-service.md
- https://docs.dataddo.com/docs/securing-credentials.md
- https://docs.dataddo.com/docs/securing-credentials
description: Authentication methods supported by Dataddo
schemes:
- type: oauth2
  name: OAuth 2.0
  evidence: OAuth 2.0 authorizers typically involve several steps, including registering your application with the data source, obtaining an access
    token, and refreshing the token as needed.
  flows:
  - App Flow
  - Authorization Code Flow
  - Refresh Token Flow
  how_to_obtain: Provide Client ID, Client Secret and Redirect URI (Authorization Code Flow) or use Dataddo‑generated URL (App Flow) as described
    in the documentation.
- type: apiKey
  name: Static credentials (non‑OAuth)
  evidence: Non-OAuth 2.0 authorizers only require to supply static values. Typically it is either a combination of a username and password or
    some static token or API key.
  location: body
  how_to_obtain: Send required static fields (e.g., client_key, username, password) in the JSON payload to the /services endpoint.
docs: https://docs.dataddo.com/headless/docs/creating-an-authorizer.md