Decentro9647 Authentication

generated: '2026-10-22'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://docs.decentro.tech/docs/testing-credentials.md
sources:
- https://docs.decentro.tech/docs/testing-credentials.md
- https://docs.decentro.tech/reference/kyc_api-sso-digilocker-revoke-token.md
- https://docs.decentro.tech/reference/digilocker-generate-access-token.md
- https://docs.decentro.tech/reference/testing-credentials-v3.md
description: Authentication methods for Decentro APIs
schemes:
- type: apiKey
  name: client_id/client_secret
  evidence: Clients are required to pass `client_id `and `client_secret `in the headers to access the APIs.
  location: header
  header: client_id, client_secret
  how_to_obtain: Provided by Decentro during onboarding or via the signup page.
- type: http-bearer
  name: JWT Bearer Token
  evidence: Customers can pass JWT in headers instead of client_id and client_secret to access the API.
  location: header
  header: Authorization
  flows:
  - client_credentials
  - refresh_token
  - user_credentials
  how_to_obtain: Generate JWT using Decentro Auth API with appropriate grant_type (client_credentials, refresh_token, or user_credentials).
docs: https://docs.decentro.tech/docs/testing-credentials.md