Annexus Health · OAuth Scopes
Annexus Health OAuth Scopes
OAuth 2.0
searched
Annexus 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.
CompanyHealthcareHealth TechnologyPatient AccessFinancial AssistanceOncologyRevenue CycleCopay AssistanceIdentityOpenID ConnectHITRUST
Scopes: 0
Flows:
Method: searched
Scopes (0)
Annexus 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.
These are the scopes the AssistPoint production authorization server advertises in its anonymous OpenID Connect discovery document. They are the standard OIDC profile set — no AssistPoint or AP Connect resource-level scopes are published. Any partner-facing API scopes are issued privately as part of an AP Connect integration agreement and were not fabricated here.
These are the scopes the AssistPoint production authorization server advertises in its anonymous OpenID Connect discovery document. They are the standard OIDC profile set — no AssistPoint or AP Connect resource-level scopes are published. Any partner-facing API scopes are issued privately as part of an AP Connect integration agreement and were not fabricated here.