Clarify Health · OAuth Scopes
Clarify Health OAuth Scopes
OAuth 2.0
probed
Clarify Health 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.
CompanyHealth TechHealthcare AnalyticsHealth DataOutcomesReferral IntelligencePayersLife Sciences
Scopes: 0
Flows:
Method: probed
Scopes (0)
Clarify Health 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.
Clarify Health publishes no scope or permission reference page — there is no developer portal to publish one on. These are the scopes the two live OIDC issuers advertise in their own discovery documents. They are ALL standard OpenID Connect / OAuth 2.0 identity scopes; not one Clarify-specific resource scope is advertised anywhere, which is the finding. A custom Okta authorization server may carry product scopes, but /oauth2/default/.well-known/openid-configuration returns 401 (E0000015) so they are not anonymously discoverable.
Clarify Health publishes no scope or permission reference page — there is no developer portal to publish one on. These are the scopes the two live OIDC issuers advertise in their own discovery documents. They are ALL standard OpenID Connect / OAuth 2.0 identity scopes; not one Clarify-specific resource scope is advertised anywhere, which is the finding. A custom Okta authorization server may carry product scopes, but /oauth2/default/.well-known/openid-configuration returns 401 (E0000015) so they are not anonymously discoverable.