ianacare · OAuth Scopes
ianacare OAuth Scopes
OAuth 2.0
probed
ianacare 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.
CompanyHealthcareCaregivingEmployee BenefitsDigital HealthCare NavigationHealth PlansMobile ApplicationIdentity
Scopes: 0
Flows:
Method: probed
Scopes (0)
ianacare 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 ianacare's own authorization server advertises in its discovery document. They are the standard OIDC/Auth0 identity scope set — ianacare publishes no API-specific permission scopes anywhere public, and no audience/API identifier is discoverable, so no resource scopes could be recorded. Nothing here was authored; every entry is copied from scopes_supported.
These are the scopes ianacare's own authorization server advertises in its discovery document. They are the standard OIDC/Auth0 identity scope set — ianacare publishes no API-specific permission scopes anywhere public, and no audience/API identifier is discoverable, so no resource scopes could be recorded. Nothing here was authored; every entry is copied from scopes_supported.
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.