Cytora · OAuth Scopes

Cytora OAuth Scopes

OAuth 2.0 searched

Cytora publishes 14 OAuth 2.0 scopes via the clientCredentials and authorizationCode flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Cytora API on a user’s behalf.

Tokens are issued from https://auth.cytora.com/oauth/token.

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.

InsuranceUnited KingdomInsurtechCommercial InsuranceUnderwritingClaimsRisk DataProperty and CasualtyReinsuranceBrokersSubmission IntakeDocument AI
Scopes: 14 Flows: clientCredentials, authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://auth.cytora.com/authorize
Token URL
https://auth.cytora.com/oauth/token
Flows
clientCredentialsauthorizationCode

Scopes (14)

ScopeDescriptionFlows
openid Request an ID token (OpenID Connect) authorizationCode
profile Basic profile claims authorizationCode
offline_access Issue a refresh token authorizationCode
name Full name claim authorizationCode
given_name Given name claim authorizationCode
family_name Family name claim authorizationCode
nickname Nickname claim authorizationCode
email Email address claim authorizationCode
email_verified Email verification state claim authorizationCode
picture Profile picture claim authorizationCode
created_at Account creation timestamp claim authorizationCode
identities Linked identity provider records claim authorizationCode
phone Phone number claim authorizationCode
address Address claim authorizationCode

Source

OAuth Scopes

cytora-scopes.yml Raw ↑
generated: '2026-07-25'
method: searched
source: https://auth.cytora.com/.well-known/openid-configuration
docs: null
note: >-
  Every scope below is a stock OpenID Connect / Auth0 identity scope advertised
  by the tenant's discovery document. Cytora publishes NO product- or
  resource-level scopes anonymously (nothing of the form risk:read,
  submission:write, claim:create). Machine-to-machine access to api.cytora.com
  uses the client_credentials grant against an API audience that is provisioned
  per customer contract and is not disclosed publicly, so the real authorization
  surface cannot be enumerated without provisioned credentials.
schemes:
- name: CytoraOAuth2
  source: well-known/cytora-openid-configuration.json
  issuer: https://auth.cytora.com/
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.cytora.com/oauth/token
  - flow: authorizationCode
    authorizationUrl: https://auth.cytora.com/authorize
    tokenUrl: https://auth.cytora.com/oauth/token
scopes:
- scope: openid
  description: Request an ID token (OpenID Connect)
  flows: [authorizationCode]
  sources: [well-known/cytora-openid-configuration.json]
- scope: profile
  description: Basic profile claims
  flows: [authorizationCode]
  sources: [well-known/cytora-openid-configuration.json]
- scope: offline_access
  description: Issue a refresh token
  flows: [authorizationCode]
  sources: [well-known/cytora-openid-configuration.json]
- scope: name
  description: Full name claim
  flows: [authorizationCode]
  sources: [well-known/cytora-openid-configuration.json]
- scope: given_name
  description: Given name claim
  flows: [authorizationCode]
  sources: [well-known/cytora-openid-configuration.json]
- scope: family_name
  description: Family name claim
  flows: [authorizationCode]
  sources: [well-known/cytora-openid-configuration.json]
- scope: nickname
  description: Nickname claim
  flows: [authorizationCode]
  sources: [well-known/cytora-openid-configuration.json]
- scope: email
  description: Email address claim
  flows: [authorizationCode]
  sources: [well-known/cytora-openid-configuration.json]
- scope: email_verified
  description: Email verification state claim
  flows: [authorizationCode]
  sources: [well-known/cytora-openid-configuration.json]
- scope: picture
  description: Profile picture claim
  flows: [authorizationCode]
  sources: [well-known/cytora-openid-configuration.json]
- scope: created_at
  description: Account creation timestamp claim
  flows: [authorizationCode]
  sources: [well-known/cytora-openid-configuration.json]
- scope: identities
  description: Linked identity provider records claim
  flows: [authorizationCode]
  sources: [well-known/cytora-openid-configuration.json]
- scope: phone
  description: Phone number claim
  flows: [authorizationCode]
  sources: [well-known/cytora-openid-configuration.json]
- scope: address
  description: Address claim
  flows: [authorizationCode]
  sources: [well-known/cytora-openid-configuration.json]
product_scopes_published: false

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/cytora-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.

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