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
https://api.insurtech.dev/auth/oauth2/token
Flows
clientCredentials
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).
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).
📄 Provider scope reference: https://learn.boostinsurance.com/docs/authentication