Ripe Insurance · OAuth Scopes

Ripe Insurance OAuth Scopes

OAuth 2.0 searched

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

Tokens are issued from https://www.ripeinsurance.co.uk/umbraco/delivery/api/v1/security/member/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 KingdomInsurtechManaging General AgentSpecialist InsurancePersonal LinesSmall Business InsuranceUnderwritingDirect to ConsumerBroker

Scopes: 2 Flows: authorizationCode, clientCredentials, refreshToken Method: searched

OAuth endpoints

Authorization URL
https://www.ripeinsurance.co.uk/umbraco/delivery/api/v1/security/member/authorize

Token URL
https://www.ripeinsurance.co.uk/umbraco/delivery/api/v1/security/member/token

Flows
authorizationCodeclientCredentialsrefreshToken

Scopes (2)

Scope	Description	Flows
openid	Standard OpenID Connect scope. Requests an ID token identifying the authenticated Ripe Insurance website member (claims: aud, exp, iat, iss, sub).	authorizationCode
offline_access	Requests a refresh token so the member session can be renewed without re-authentication.	authorizationCode

📄 Provider scope reference: https://docs.umbraco.com/umbraco-cms/reference/content-delivery-api#protected-content

Source

OAuth Scopes

generated: '2026-07-25'
method: searched
source: https://www.ripeinsurance.co.uk/.well-known/openid-configuration (fetched 2026-07-25)
docs: https://docs.umbraco.com/umbraco-cms/reference/content-delivery-api#protected-content
note: >-
  Neither harvested OpenAPI declares an oauth2 securityScheme, so the mechanical
  derivation (0-working/derive-oauth-scopes.py) returned nothing. The scopes below were
  read from the live OpenID Connect discovery document published by the Umbraco
  (OpenIddict) member-authentication server. This is the WEBSITE CUSTOMER LOGIN scope
  surface, not a partner or developer API scope surface — Ripe publishes no developer
  scopes because it publishes no developer API. Recorded because it is real and
  anonymously readable.
schemes:
- name: umbraco-member-oidc
  type: openIdConnect
  source: well-known/ripe-insurance-openid-configuration.json
  issuer: https://www.ripeinsurance.co.uk/
  flows:
  - flow: authorizationCode
    authorizationUrl: https://www.ripeinsurance.co.uk/umbraco/delivery/api/v1/security/member/authorize
    tokenUrl: https://www.ripeinsurance.co.uk/umbraco/delivery/api/v1/security/member/token
    pkce: [S256, plain]
  - flow: clientCredentials
    tokenUrl: https://www.ripeinsurance.co.uk/umbraco/delivery/api/v1/security/member/token
  - flow: refreshToken
    tokenUrl: https://www.ripeinsurance.co.uk/umbraco/delivery/api/v1/security/member/token
scopes:
- scope: openid
  description: >-
    Standard OpenID Connect scope. Requests an ID token identifying the authenticated
    Ripe Insurance website member (claims: aud, exp, iat, iss, sub).
  flows: [authorizationCode]
  sources: [well-known/ripe-insurance-openid-configuration.json]
  standard: OpenID Connect Core 1.0
- scope: offline_access
  description: >-
    Requests a refresh token so the member session can be renewed without
    re-authentication.
  flows: [authorizationCode]
  sources: [well-known/ripe-insurance-openid-configuration.json]
  standard: OpenID Connect Core 1.0
coverage:
  scopes_total: 2
  vendor_standard: 2
  provider_specific: 0
  note: >-
    Zero provider-specific scopes. Every scope advertised is an unmodified OpenID
    Connect standard scope emitted by the CMS default configuration — there is no
    resource-scoped permission model (no read:policy, no quote:create, nothing
    insurance-shaped) because no insurance API is exposed.