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
Flows
authorizationCodeurn:ietf:params:oauth:grant-type:jwt-bearerciba

Scopes (4)

ScopeDescriptionFlows
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.

Source

OAuth Scopes

aduna-scopes.yml Raw ↑
generated: '2026-07-25'
method: searched
source: >-
  https://github.com/adunaglobal/nv2-asp-server-java-aduna-sdk/blob/main/backend/src/main/java/com/adunaglobal/sdk/backend/configuration/NumberVerificationProperties.java
docs: https://docs.adunaglobal.com/how-to-enable-an-api/number-verification-api-v-2.1-landing-page
docs_gated: true
note: >-
  Aduna publishes no OpenAPI and its scope reference sits behind the portal login wall. These
  scopes are read verbatim from the default values in Aduna's own source-available Java SDK
  configuration class and are restated in the SDK README configuration table. They follow the
  CAMARA convention of pairing an OIDC scope with a W3C DPV purpose and a per-operation API scope.
  Only the Number Verification API's scopes are publicly visible; the SIM Swap, KYC Match and
  roadmap APIs will have their own CAMARA scopes but none are published.
schemes:
- name: Aduna authorization (network- and SIM-based)
  source: authentication/aduna-authentication.yml
  flows:
  - flow: authorizationCode
    tokenUrl: '{baseURL}/auth/token'
  - flow: urn:ietf:params:oauth:grant-type:jwt-bearer
    tokenUrl: '{baseURL}/auth/token'
  - flow: ciba
    backchannelAuthorizationUrl: '{baseURL}/auth/bc-authorize'
    tokenUrl: '{baseURL}/auth/token'
scopes:
- scope: openid
  description: OpenID Connect authentication; required on every Aduna Number Verification request.
  kind: oidc
  operations: [verify, read]
- scope: dpv:FraudPreventionAndDetection
  description: >-
    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.
  kind: purpose
  operations: [verify, read]
- scope: number-verification:verify
  description: >-
    Verify that a supplied phone number matches the phone number of the device holding the
    authenticated SIM. Backs POST /number-verification/v2/verify.
  kind: api
  operations: [verify]
- scope: number-verification:device-phone-number:read
  description: >-
    Retrieve the phone number of the device holding the authenticated SIM (number share). Backs
    GET /number-verification/v2/device-phone-number.
  kind: api
  operations: [read]
scope_sets:
- operation: verify
  property: com.adunaglobal.sdk.backend.api.numberVerification.verifyScopes
  value: openid dpv:FraudPreventionAndDetection number-verification:verify
- operation: read
  property: com.adunaglobal.sdk.backend.api.numberVerification.readScopes
  value: openid dpv:FraudPreventionAndDetection number-verification:device-phone-number:read

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this
  • find_scopesBrowse and filter every scope set in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This scope set
curl "https://apis.io/api/v1/scopes/aduna-scopes"
All oauth scopes
curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.