KPN · OAuth Scopes
KPN OAuth Scopes
OAuth 2.0
derived
KPN 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.
Tokens are issued from https://api-prd.kpn.com/oauth/client_credential/accesstoken?grant_type=client_credentials.
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.
TelecommunicationsNetherlandsMobile Network OperatorBroadbandNetwork APIsCAMARAOpen GatewaySIM SwapIdentity VerificationMessagingSMSVoiceIoTLoRaWANFiberWholesale5GEurope
Scopes: 0
Flows: clientCredentials
Method: derived
OAuth endpoints
Token URL
https://api-prd.kpn.com/oauth/client_credential/accesstoken?grant_type=client_credentials https://api-prd.kpn.com/oauth/grip/msm/accesstoken?grant_type=client_credentials
https://api-prd.kpn.com/oauth/client_credential/accesstoken?grant_type=client_credentials https://api-prd.kpn.com/oauth/grip/msm/accesstoken?grant_type=client_credentials
Flows
clientCredentials
clientCredentials
Scopes (0)
KPN 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.
📄 Provider scope reference: https://developer.kpn.com/page/getting-started