Wix · OAuth Scopes
Wix OAuth Scopes
OAuth 2.0
derived
Wix 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://www.wixapis.com/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.
CMSeCommerceHeadlessWebsite Builder
Scopes: 0
Flows: authorizationCode
Method: derived
OAuth endpoints
Authorization URL
https://www.wix.com/installer/install
https://www.wix.com/installer/install
Token URL
https://www.wixapis.com/oauth2/token
https://www.wixapis.com/oauth2/token
Flows
authorizationCode
authorizationCode
Scopes (0)
Wix 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.
Wix OAuth does not use scope strings in the authorization flow; app permissions are granted as permission scopes configured in the app dashboard (GUID-identified via the App Permissions API) and documented per endpoint in the API reference, with no aggregated published scopes list (see https://dev.wix.com/docs/build-apps/develop-your-app/access/authorization/about-permissions).
Wix OAuth does not use scope strings in the authorization flow; app permissions are granted as permission scopes configured in the app dashboard (GUID-identified via the App Permissions API) and documented per endpoint in the API reference, with no aggregated published scopes list (see https://dev.wix.com/docs/build-apps/develop-your-app/access/authorization/about-permissions).
📄 Provider scope reference: https://dev.wix.com/docs/build-apps/develop-your-app/access/authorization/about-permissions