Aduna · OAuth Scopes
Aduna OAuth Scopes
OAuth 2.0
searched
Aduna publishes 4 OAuth 2.0 scopes via the authorizationCode, urn:ietf:params:oauth:grant-type:jwt-bearer, and ciba flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Aduna API on a user’s behalf.
Tokens are issued from {baseURL}/auth/token.
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.
TelecommunicationsSwedenNetwork APIsCAMARAOpen GatewayAPI AggregatorIdentity VerificationSIM SwapNumber VerificationFraud PreventionQuality on DemandDevice LocationEricsson
Scopes: 4
Flows: authorizationCode, urn:ietf:params:oauth:grant-type:jwt-bearer, ciba
Method: searched
OAuth endpoints
Token URL
{baseURL}/auth/token
{baseURL}/auth/token
Flows
authorizationCodeurn:ietf:params:oauth:grant-type:jwt-bearerciba
authorizationCodeurn:ietf:params:oauth:grant-type:jwt-bearerciba
Scopes (4)
| Scope | Description | Flows |
|---|---|---|
| openid | OpenID Connect authentication; required on every Aduna Number Verification request. | |
| dpv:FraudPreventionAndDetection | W3C Data Privacy Vocabulary purpose scope declaring that the personal data is processed for fraud prevention and detection. CAMARA requires a dpv purpose alongside the API scope. | |
| number-verification:verify | Verify that a supplied phone number matches the phone number of the device holding the authenticated SIM. Backs POST /number-verification/v2/verify. | |
| number-verification:device-phone-number:read | Retrieve the phone number of the device holding the authenticated SIM (number share). Backs GET /number-verification/v2/device-phone-number. |
📄 Provider scope reference: https://docs.adunaglobal.com/how-to-enable-an-api/number-verification-api-v-2.1-landing-page