Jellyvision · OAuth Scopes
Jellyvision OAuth Scopes
OAuth 2.0
searched
Jellyvision 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.
CompanyEmployee BenefitsHuman ResourcesBenefits AdministrationBenefits EnrollmentHealth InsuranceDecision SupportHR TechnologyInsuranceEmployee Engagement
Scopes: 0
Flows:
Method: searched
Scopes (0)
Jellyvision 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.
Jellyvision does not publish a scope/permission reference page. The single Partner Integration API scope below is read from the decoded JWT access-token example printed in the authentication section of the public API reference. The second scope is read from the RFC 9728 protected-resource metadata served at https://www.jellyvision.com/.well-known/oauth-protected-resource and applies to the MCP server on the marketing site, not to the Partner Integration API.
Jellyvision does not publish a scope/permission reference page. The single Partner Integration API scope below is read from the decoded JWT access-token example printed in the authentication section of the public API reference. The second scope is read from the RFC 9728 protected-resource metadata served at https://www.jellyvision.com/.well-known/oauth-protected-resource and applies to the MCP server on the marketing site, not to the Partner Integration API.
📄 Provider scope reference: https://partner-api-docs.myalex.com/
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.