AppyWay · OAuth Scopes
AppyWay OAuth Scopes
OAuth 2.0
derived
AppyWay 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://auth.appyway.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.
ParkingTrafficUrban MobilitySmart CitiesEV Charging
Scopes: 0
Flows: authorizationCode
Method: derived
OAuth endpoints
Authorization URL
https://auth.appyway.com/authorize
https://auth.appyway.com/authorize
Token URL
https://auth.appyway.com/oauth/token
https://auth.appyway.com/oauth/token
Flows
authorizationCode
authorizationCode
Scopes (0)
AppyWay 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.
AppyWay does not publish OAuth scopes; its authentication docs state API requests are authenticated using API keys, with invalid keys returning 401 Unauthorized (https://docs.appyway.com/docs/public-docs/50055c042f423-authentication).
AppyWay does not publish OAuth scopes; its authentication docs state API requests are authenticated using API keys, with invalid keys returning 401 Unauthorized (https://docs.appyway.com/docs/public-docs/50055c042f423-authentication).
📄 Provider scope reference: https://docs.appyway.com/docs/public-docs/50055c042f423-authentication