Kameleoon · OAuth Scopes
Kameleoon OAuth Scopes
OAuth 2.0
derived
Kameleoon 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.kameleoon.com/oauth/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.
ExperimentationAB TestingPersonalizationFeature FlagsAI
Scopes: 0
Flows: clientCredentials, authorizationCode
Method: derived
OAuth endpoints
Authorization URL
https://api.kameleoon.com/oauth/authorize
https://api.kameleoon.com/oauth/authorize
Token URL
https://api.kameleoon.com/oauth/token
https://api.kameleoon.com/oauth/token
Flows
clientCredentialsauthorizationCode
clientCredentialsauthorizationCode
Scopes (0)
Kameleoon 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.
Kameleoon's Automation API uses OAuth 2.0 client credentials and authorization code flows but does not document any OAuth scopes; access is tied to the Kameleoon user account behind the API credentials (https://docs.kameleoon.com/developer-docs/apis/automation-api-rest/get-started/get-started).
Kameleoon's Automation API uses OAuth 2.0 client credentials and authorization code flows but does not document any OAuth scopes; access is tied to the Kameleoon user account behind the API credentials (https://docs.kameleoon.com/developer-docs/apis/automation-api-rest/get-started/get-started).
📄 Provider scope reference: https://docs.kameleoon.com/developer-docs/apis/automation-api-rest/get-started/get-started