Ki Insurance · OAuth Scopes

Ki Insurance OAuth Scopes

OAuth 2.0 searched

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

Tokens are issued from https://login.ki-insurance.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 KingdomLloyd's of LondonSpecialty InsuranceProperty and CasualtyUnderwritingInsurtechBrokerAlgorithmic UnderwritingReinsurance

Scopes: 14 Flows: authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://login.ki-insurance.com/authorize

Token URL
https://login.ki-insurance.com/oauth/token

Flows
authorizationCode

Scopes (14)

Scope	Description	Flows
openid	Standard OIDC scope — request an ID token for the authenticated broker user.	authorizationCode
profile	Standard OIDC scope — name, nickname and picture claims.	authorizationCode
email	Standard OIDC scope — email and email_verified claims.	authorizationCode
offline_access	Standard OAuth scope — issue a refresh token for the broker session.	authorizationCode
address	Standard OIDC scope — address claim.	authorizationCode
phone	Standard OIDC scope — phone_number claim.	authorizationCode
name	Auth0 profile sub-scope — name claim.	authorizationCode
given_name	Auth0 profile sub-scope — given_name claim.	authorizationCode
family_name	Auth0 profile sub-scope — family_name claim.	authorizationCode
nickname	Auth0 profile sub-scope — nickname claim.	authorizationCode
picture	Auth0 profile sub-scope — picture claim.	authorizationCode
email_verified	Auth0 profile sub-scope — email_verified claim.	authorizationCode
created_at	Auth0 profile sub-scope — created_at claim.	authorizationCode
identities	Auth0 profile sub-scope — linked identities claim.	authorizationCode

📄 Provider scope reference: https://login.ki-insurance.com/.well-known/openid-configuration

Source

OAuth Scopes

generated: '2026-07-25'
method: searched
source: https://login.ki-insurance.com/.well-known/openid-configuration
docs: https://login.ki-insurance.com/.well-known/openid-configuration
summary: >-
  Ki's authorization server publishes only the standard OpenID Connect scopes.
  No Ki business scope (quote:read, quote:write, pipeline:read or similar) is
  advertised anywhere on the public surface, and none appears in the platform
  client bundle — the broker app requests a token for audience
  https://api.ki.com and authorises every /api call with that single bearer
  token. Any partner-specific scope model, if one exists, is private.
schemes:
- name: auth0OAuth2
  source: https://login.ki-insurance.com/.well-known/openid-configuration
  audience: https://api.ki.com
  flows:
  - flow: authorizationCode
    authorizationUrl: https://login.ki-insurance.com/authorize
    tokenUrl: https://login.ki-insurance.com/oauth/token
scopes:
- scope: openid
  description: Standard OIDC scope — request an ID token for the authenticated broker user.
  flows: [authorizationCode]
  sources: [https://login.ki-insurance.com/.well-known/openid-configuration]
- scope: profile
  description: Standard OIDC scope — name, nickname and picture claims.
  flows: [authorizationCode]
  sources: [https://login.ki-insurance.com/.well-known/openid-configuration]
- scope: email
  description: Standard OIDC scope — email and email_verified claims.
  flows: [authorizationCode]
  sources: [https://login.ki-insurance.com/.well-known/openid-configuration]
- scope: offline_access
  description: Standard OAuth scope — issue a refresh token for the broker session.
  flows: [authorizationCode]
  sources: [https://login.ki-insurance.com/.well-known/openid-configuration]
- scope: address
  description: Standard OIDC scope — address claim.
  flows: [authorizationCode]
  sources: [https://login.ki-insurance.com/.well-known/openid-configuration]
- scope: phone
  description: Standard OIDC scope — phone_number claim.
  flows: [authorizationCode]
  sources: [https://login.ki-insurance.com/.well-known/openid-configuration]
- scope: name
  description: Auth0 profile sub-scope — name claim.
  flows: [authorizationCode]
  sources: [https://login.ki-insurance.com/.well-known/openid-configuration]
- scope: given_name
  description: Auth0 profile sub-scope — given_name claim.
  flows: [authorizationCode]
  sources: [https://login.ki-insurance.com/.well-known/openid-configuration]
- scope: family_name
  description: Auth0 profile sub-scope — family_name claim.
  flows: [authorizationCode]
  sources: [https://login.ki-insurance.com/.well-known/openid-configuration]
- scope: nickname
  description: Auth0 profile sub-scope — nickname claim.
  flows: [authorizationCode]
  sources: [https://login.ki-insurance.com/.well-known/openid-configuration]
- scope: picture
  description: Auth0 profile sub-scope — picture claim.
  flows: [authorizationCode]
  sources: [https://login.ki-insurance.com/.well-known/openid-configuration]
- scope: email_verified
  description: Auth0 profile sub-scope — email_verified claim.
  flows: [authorizationCode]
  sources: [https://login.ki-insurance.com/.well-known/openid-configuration]
- scope: created_at
  description: Auth0 profile sub-scope — created_at claim.
  flows: [authorizationCode]
  sources: [https://login.ki-insurance.com/.well-known/openid-configuration]
- scope: identities
  description: Auth0 profile sub-scope — linked identities claim.
  flows: [authorizationCode]
  sources: [https://login.ki-insurance.com/.well-known/openid-configuration]
authorization_model:
  note: >-
    Authorisation inside the Ki platform is role- and entitlement-based rather
    than scope-based. The client bundle carries an admin surface
    (/api/system/admin/*, /api/maxlinesizes, bulk user management) and a
    per-user class-of-business entitlement (/api/user/{userId}/selected-cobs),
    which implies server-side role checks — the 403 handling in the client
    confirms it. None of that is published as OAuth scopes.
gaps:
- No Ki-specific API scopes are published.
- No scope-to-operation mapping exists; do not infer one.