Zinnia · OAuth Scopes

Zinnia OAuth Scopes

OAuth 2.0 probed

Zinnia 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.

InsuranceLife InsuranceAnnuitiesPolicy AdministrationInsurtechFinancial-ServicesThird Party AdministrationNew BusinessOrder EntryDocument-ManagementUnderwritingEnterprise

Scopes: 0 Flows: Method: probed

Scopes (0)

Zinnia 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 OIDC identity scopes the Zinnia Auth0 tenant advertises, not API permissions. Zinnia carries API authorization in a custom claim - the Kong OpenID Connect plugin config in every published spec sets scopes_claim to "https://api.zinnia.io/permissions" (dev/qa/uat variants use the matching environment host) and requires an "aud" of the environment API host. The permission values themselves are issued per partner tenant and are not published, so the API-level scope list cannot be enumerated from public material.

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-09-13'
method: probed
source: https://login.zinnia.com/.well-known/openid-configuration (HTTP 200) plus the x-kong-security-openid-connect scopes_claim declared in the published OpenAPI securitySchemes
provider: Auth0 tenant at https://login.zinnia.com/
issuer: https://login.zinnia.com/
scopes_claim: https://api.zinnia.io/permissions
scope_count: 14
scopes:
- name: openid
  description: OpenID Connect standard scope advertised by the Zinnia Auth0 tenant discovery document.
- name: profile
  description: OpenID Connect standard scope advertised by the Zinnia Auth0 tenant discovery document.
- name: offline_access
  description: OpenID Connect standard scope advertised by the Zinnia Auth0 tenant discovery document.
- name: name
  description: OpenID Connect standard scope advertised by the Zinnia Auth0 tenant discovery document.
- name: given_name
  description: OpenID Connect standard scope advertised by the Zinnia Auth0 tenant discovery document.
- name: family_name
  description: OpenID Connect standard scope advertised by the Zinnia Auth0 tenant discovery document.
- name: nickname
  description: OpenID Connect standard scope advertised by the Zinnia Auth0 tenant discovery document.
- name: email
  description: OpenID Connect standard scope advertised by the Zinnia Auth0 tenant discovery document.
- name: email_verified
  description: OpenID Connect standard scope advertised by the Zinnia Auth0 tenant discovery document.
- name: picture
  description: OpenID Connect standard scope advertised by the Zinnia Auth0 tenant discovery document.
- name: created_at
  description: OpenID Connect standard scope advertised by the Zinnia Auth0 tenant discovery document.
- name: identities
  description: OpenID Connect standard scope advertised by the Zinnia Auth0 tenant discovery document.
- name: phone
  description: OpenID Connect standard scope advertised by the Zinnia Auth0 tenant discovery document.
- name: address
  description: OpenID Connect standard scope advertised by the Zinnia Auth0 tenant discovery document.
note: These are the OIDC identity scopes the Zinnia Auth0 tenant advertises, not API permissions. Zinnia carries API authorization in a custom claim - the Kong OpenID Connect plugin config in every published
  spec sets scopes_claim to "https://api.zinnia.io/permissions" (dev/qa/uat variants use the matching environment host) and requires an "aud" of the environment API host. The permission values themselves
  are issued per partner tenant and are not published, so the API-level scope list cannot be enumerated from public material.
audiences:
- https://api.zinnia.io
- https://dev.api.zinnia.io
- https://uat.api.zinnia.io
authorization_servers:
- environment: production
  issuer: https://login.zinnia.com/
  discovery: https://login.zinnia.com/.well-known/openid-configuration
  status: 200
- environment: uat
  issuer: https://login.uat.zinnia.com/
  discovery: https://login.uat.zinnia.com/.well-known/openid-configuration
  status: 200
- environment: qa
  issuer: https://login.qa.zinnia.com/
  discovery: https://login.qa.zinnia.com/.well-known/openid-configuration
  status: 200
- environment: dev
  issuer: https://login.dev.zinnia.com/
  discovery: https://login.dev.zinnia.com/.well-known/openid-configuration
  status: 200
additional_issuers_allowed:
- https://login.mypolicyview.com/

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This scope set

curl "https://apis.io/api/v1/scopes/zinnia-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.