Sentry Insurance · OAuth Scopes
Sentry Insurance OAuth Scopes
OAuth 2.0
probed
Sentry Insurance 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.
Fortune 1000InsuranceProperty and Casualty InsuranceCommercial InsuranceWorkers CompensationAuto InsuranceRetirementAnnuitiesMutual InsuranceFinancial-ServicesTruckingWisconsinUnited States
Scopes: 0
Flows:
Method: probed
Scopes (0)
Sentry Insurance 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.
These are the scopes the Sentry Insurance Okta tenant (account.sentry.com) advertises in its published OIDC/OAuth 2.0 metadata. They are the stock OpenID Connect set plus Okta's myAccount self-service family and one tenant-specific scope (`interclient_access`). Sentry Insurance publishes NO scope reference page and no business-domain scopes — there is no product API for a scope to protect. Recorded verbatim from the metadata, not curated.
These are the scopes the Sentry Insurance Okta tenant (account.sentry.com) advertises in its published OIDC/OAuth 2.0 metadata. They are the stock OpenID Connect set plus Okta's myAccount self-service family and one tenant-specific scope (`interclient_access`). Sentry Insurance publishes NO scope reference page and no business-domain scopes — there is no product API for a scope to protect. Recorded verbatim from the metadata, not curated.
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.