Nokia · OAuth Scopes

Nokia OAuth Scopes

OAuth 2.0 searched

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

Telecommunications5G6GMobile NetworkNetwork InfrastructureIP NetworksOptical NetworksFixed NetworksBroadbandService RouterSR OSSR LinuxWaveSuiteNSPNetwork Services PlatformNetwork as CodeCAMARANetwork ExposureOpen GatewayYANGNetwork AutomationCSPBell LabsSubmarine CableFiber7x50
Scopes: 0 Flows: Method: searched

Scopes (0)

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

The RapidAPI contract declares only an apiKey scheme, so no oauth2 scopes could be derived from it (derive-oauth-scopes.py: 0). These scopes are the consent and authorization scopes the docs publish for the NaC Authorization Server (CIBA / Authorization Code flows) and the Consent & Authorization form. Purpose may be prefixed per W3C DPV, e.g. "dpv:FraudPreventionAndDetection number-verification:verify".

📄 Provider scope reference: https://networkascode.nokia.io/docs/general-concepts/consent-identity-mgmt#available-scopes

Source

OAuth Scopes

Raw ↑ 
generated: '2026-11-04'
method: searched
source: https://networkascode.nokia.io/docs/general-concepts/consent-identity-mgmt
docs: https://networkascode.nokia.io/docs/general-concepts/consent-identity-mgmt#available-scopes
name: Nokia Network as Code consent scopes
note: >-
  The RapidAPI contract declares only an apiKey scheme, so no oauth2 scopes could
  be derived from it (derive-oauth-scopes.py: 0). These scopes are the consent
  and authorization scopes the docs publish for the NaC Authorization Server
  (CIBA / Authorization Code flows) and the Consent & Authorization form. Purpose
  may be prefixed per W3C DPV, e.g. "dpv:FraudPreventionAndDetection number-verification:verify".
purposes:
  - id: dpv:FraudPreventionAndDetection
    description: Action is performed to detect and prevent fraudulent actions. For example, to validate the user is legitimate.
  - id: dpv:RequestedServiceProvision
    description: Processing is necessary to provide a service requested by the user.
scopes:
  - id: device-roaming-status:read
    description: Get device roaming status
    group: Device Status
  - id: device-reachability-status:read
    description: Get device reachability status
    group: Device Status
  - id: location-verification:verify
    description: Verify the location
    group: Location
  - id: location-retrieval:read
    description: Get the location of a device
    group: Location
  - id: geofencing-subscriptions:read
    description: Retrieving list of active geofencing subscriptions
    group: Geofencing
  - id: geofencing-subscriptions:delete
    description: Deletion of active geofencing subscriptions
    group: Geofencing
  - id: specialized-network-read
    description: Get slice information
    group: Specialized Networks
  - id: specialized-network-create
    description: Create a slice
    group: Specialized Networks
  - id: specialized-network-delete
    description: Delete a slice
    group: Specialized Networks
  - id: specialized-network-activate
    description: Activate a slice
    group: Specialized Networks
  - id: specialized-network-deactivate
    description: Deactivate a slice
    group: Specialized Networks
  - id: specialized-network-attach-device
    description: Attach device to a slice
    group: Specialized Networks
  - id: specialized-network-detach-device
    description: Detach a device from a slice
    group: Specialized Networks
  - id: congestion-insight
    description: Get Congestion Insights on devices
    group: Congestion Insights
  - id: number-verification:verify
    description: Verify if a device is using the phone number informed by the user.
    group: Number Verification
  - id: device-swap:check
    description: Verify a SIM card has been moved to a new device
    group: Device Swap
  - id: device-swap:retrieve-date
    description: Retrieve date of the last device swap.
    group: Device Swap
  - id: sim-swap:check
    description: Check if a SIM swap has occurred
    group: SIM Swap
  - id: sim-swap:retrieve-date
    description: Retrieve the date of the last SIM swap
    group: SIM Swap
  - id: number-recycling:check
    description: Check whether the subscriber associated with a phone number has changed
    group: Number Recycling
  - id: consent-info:retrieve
    description: Retrieve the validity status of data processing for scopes and a purpose
    group: Consent Info
  - id: kyc-match:match
    description: Perform a customer match check
    group: KYC
  - id: kyc-age-verification:verify
    description: Perform an age verification on a customer
    group: KYC
  - id: kyc-tenure:check-tenure
    description: Perform a subscriber tenure check
    group: KYC
  - id: kyc-fill-in:set-all
    description: Request all fields related to the user.
    group: KYC Fill-in
  - id: kyc-fill-in:name
    description: Requests full name information for the user.
    group: KYC Fill-in
  - id: kyc-fill-in:address
    description: Requests complete address information for the user, including street and postal details.
    group: KYC Fill-in
  - id: kyc-fill-in:region
    description: Requests region or prefecture (province/state) information for the user's address.
    group: KYC Fill-in
  - id: kyc-fill-in:locality
    description: Requests locality (city/town) information for the user's address.
    group: KYC Fill-in
  - id: kyc-fill-in:country
    description: Requests country code (ISO 3166-1 alpha-2 format) associated with the user's address.
    group: KYC Fill-in
  - id: kyc-fill-in:birthdate
    description: Requests birthdate information of the customer, in ISO 8601 date format.
    group: KYC Fill-in
  - id: kyc-fill-in:email
    description: Requests email address associated with the customer stored on Operator's system.
    group: KYC Fill-in
  - id: kyc-fill-in:gender
    description: Requests gender (Male/Female/Other) of the customer from Operator's system records.
    group: KYC Fill-in
  - id: kyc-fill-in:nationality
    description: Requests nationality (ISO 3166-1 alpha-2 code) associated with the user's ID document(s)
    group: KYC Fill-in
  - id: other
    description: Refer to other desired scopes, which are not listed here
    group: Other

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/nokia-corp-scopes"
All oauth scopes 
curl "https://apis.io/api/v1/scopes?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.

GitHub Google LinkedIn

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