Boost Insurance · OAuth Scopes

Boost Insurance OAuth Scopes

OAuth 2.0 derived

Boost Insurance 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.

Tokens are issued from https://api.insurtech.dev/auth/oauth2/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.

InsuranceEmbedded InsuranceInsurance-as-a-ServicePolicy AdministrationClaims
Scopes: 0 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
https://api.insurtech.dev/auth/oauth2/token
Flows
clientCredentials

Scopes (0)

Boost Insurance 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.

Boost uses the OAuth 2.0 Client Credentials grant with a Client ID and Client Secret, and does not publish any OAuth scopes; access is governed by partner credentials rather than scoped tokens (https://learn.boostinsurance.com/docs/authentication).

Source

OAuth Scopes

boost-insurance-scopes.yml Raw ↑
generated: '2026-07-11'
method: derived
source: openapi/boost-insurance-openapi.yml
docs: https://learn.boostinsurance.com/docs/authentication
note: Boost uses the OAuth 2.0 Client Credentials grant with a Client ID and Client
  Secret, and does not publish any OAuth scopes; access is governed by partner credentials
  rather than scoped tokens (https://learn.boostinsurance.com/docs/authentication).
schemes:
- name: boostOAuth
  source: openapi/boost-insurance-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api.insurtech.dev/auth/oauth2/token
  description: OAuth 2.0 Client Credentials grant. Tokens are obtained from the Boost authentication
    endpoint and presented as a Bearer token.
scopes: []