UPS · OAuth Scopes
UPS OAuth Scopes
OAuth 2.0
derived
UPS 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://onlinetools.ups.com/api/security/v1/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.
LogisticsShippingFortune 500Supply Chain
Scopes: 0
Flows: clientCredentials
Method: derived
OAuth endpoints
Token URL
https://onlinetools.ups.com/api/security/v1/oauth/token
https://onlinetools.ups.com/api/security/v1/oauth/token
Flows
clientCredentials
clientCredentials
Scopes (0)
UPS 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.
UPS OAuth 2.0 does not publish named scopes — the client credentials token request takes no scope parameter and the authorization-code spec leaves scope as an undocumented free-form string, with API permissions instead granted by adding API products to an application in the UPS Developer Portal (https://developer.ups.com/api/reference/oauth/client-credentials).
UPS OAuth 2.0 does not publish named scopes — the client credentials token request takes no scope parameter and the authorization-code spec leaves scope as an undocumented free-form string, with API permissions instead granted by adding API products to an application in the UPS Developer Portal (https://developer.ups.com/api/reference/oauth/client-credentials).
📄 Provider scope reference: https://developer.ups.com/api/reference/oauth/client-credentials