Express Scripts Holding · OAuth Scopes
Express Scripts Holding OAuth Scopes
OAuth 2.0
probed
Express Scripts Holding publishes 10 OAuth 2.0 scopes. Scopes are the fine-grained permissions an application requests at authorization time to act against the Express Scripts Holding API on a user’s behalf.
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.
HealthHealthcarePharmacyPharmacy Benefit ManagementPrescriptionsClaimsFortune 100
Scopes: 10
Flows:
Method: probed
Scopes (10)
| Scope | Description | Flows |
|---|---|---|
| esrx.default | The Express Scripts application scope requested by the developer portal client. This is the only vendor-namespaced scope observed in the estate. What it grants is not published; the scope name is recorded, its permissions are not known. | |
| openid | Requests an ID token. Required for any OIDC flow. | |
| profile | Basic profile claims (name, preferred_username, locale, updated_at). | |
| email and email_verified claims. | ||
| address | The address claim. | |
| phone | phone_number and phone_number_verified claims. | |
| offline_access | Requests a refresh token. | |
| groups | Group membership claim. Advertised on the org authorization server. | |
| device_sso | Okta device single sign-on. | |
| interclient_access | Okta cross-client token exchange. |
Source
OAuth Scopes
Work with this as data
Every scope set here is available over the APIs.io API and to AI agents over MCP.