Daon · OAuth Scopes
Daon OAuth Scopes
OAuth 2.0
none
Daon uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.
This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.
CompanyDigital IdentityIdentity VerificationAuthenticationBiometricsFraud PreventionMulti-Factor AuthenticationFIDO
Scopes: 0
Flows:
Method: none
Scopes (0)
Daon implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.
TrustX API uses JWT bearer tokens with permissions embedded in the token (e.g., TNT#{tenantid}#ArthrServer:listTenantApiKeys), not OAuth scopes.
TrustX API uses JWT bearer tokens with permissions embedded in the token (e.g., TNT#{tenantid}#ArthrServer:listTenantApiKeys), not OAuth scopes.
Source
OAuth Scopes
Work with this as data
Every scope set here is available over the APIs.io API and to AI agents over MCP.