Express Scripts Holding · OAuth Scopes
Express Scripts Holding OAuth Scopes
OAuth 2.0
probed
Express Scripts Holding 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.
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: 0
Flows:
Method: probed
Scopes (0)
Express Scripts Holding 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.
No scopes/permissions reference page is publicly reachable — the developer portal renders client-side and its content backend answers 403 to anonymous requests. Everything below is read from documents the provider serves anonymously. The one Express Scripts-specific scope in the estate is `esrx.default`; every other scope advertised on the default authorization server is a standard OIDC or Okta scope.
No scopes/permissions reference page is publicly reachable — the developer portal renders client-side and its content backend answers 403 to anonymous requests. Everything below is read from documents the provider serves anonymously. The one Express Scripts-specific scope in the estate is `esrx.default`; every other scope advertised on the default authorization server is a standard OIDC or Okta scope.
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.