Infor · OAuth Scopes
Infor OAuth Scopes
OAuth 2.0
derived
Infor 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://inforos.infor.com/INFOR_DEV/as/token.oauth2.
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.
ERPManufacturingSupply ChainCloudIntegration
Scopes: 0
Flows: clientCredentials, authorizationCode
Method: derived
OAuth endpoints
Authorization URL
https://inforos.infor.com/INFOR_DEV/as/authorization.oauth2
https://inforos.infor.com/INFOR_DEV/as/authorization.oauth2
Token URL
https://inforos.infor.com/INFOR_DEV/as/token.oauth2
https://inforos.infor.com/INFOR_DEV/as/token.oauth2
Flows
clientCredentialsauthorizationCode
clientCredentialsauthorizationCode
Scopes (0)
Infor 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.
Infor does not publish a fixed catalog of OAuth scope strings; ION API Gateway scopes are defined and attached per authorized app or service account by tenant administrators (see "Adding scopes for authorized apps or service accounts", https://docs.infor.com/inforos/2026.x/en-us/useradminlib_cloud/apigatewayag_cloud/vya1611685179822.html).
Infor does not publish a fixed catalog of OAuth scope strings; ION API Gateway scopes are defined and attached per authorized app or service account by tenant administrators (see "Adding scopes for authorized apps or service accounts", https://docs.infor.com/inforos/2026.x/en-us/useradminlib_cloud/apigatewayag_cloud/vya1611685179822.html).
📄 Provider scope reference: https://docs.infor.com/inforos/2026.x/en-us/useradminlib_cloud/apigatewayag_cloud/vya1611685179822.html