Alteryx · OAuth Scopes
Alteryx OAuth Scopes
OAuth 2.0
derived
Alteryx 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://{serverHostname}/webapi/oauth2/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.
AnalyticsAutomationData EngineeringData PreparationData ScienceETLMachine LearningPredictive Analytics
Scopes: 0
Flows: clientCredentials
Method: derived
OAuth endpoints
Token URL
https://{serverHostname}/webapi/oauth2/token
https://{serverHostname}/webapi/oauth2/token
Flows
clientCredentials
clientCredentials
Scopes (0)
Alteryx 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.
Alteryx Server API v3 uses an OAuth 2.0 client_credentials flow with an API Access Key and Secret from the user's Server profile, and access is governed by Server roles (e.g. admin enablement) rather than OAuth scopes; no scopes are documented (https://help.alteryx.com/current/en/server/api-overview/alteryx-server-api-v3/server-api-configuration-and-authorization.html).
Alteryx Server API v3 uses an OAuth 2.0 client_credentials flow with an API Access Key and Secret from the user's Server profile, and access is governed by Server roles (e.g. admin enablement) rather than OAuth scopes; no scopes are documented (https://help.alteryx.com/current/en/server/api-overview/alteryx-server-api-v3/server-api-configuration-and-authorization.html).
📄 Provider scope reference: https://help.alteryx.com/current/en/server/api-overview/alteryx-server-api-v3/server-api-configuration-and-authorization.html