Coterie Insurance OAuth Scopes

OAuth 2.0 derived

Coterie 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.coterieinsurance.com/v1/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.

InsuranceCommercial InsuranceSmall BusinessEmbedded InsuranceInsurtech

Scopes: 0 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
https://api.coterieinsurance.com/v1/oauth/token

Flows
clientCredentials

Scopes (0)

Coterie 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.

Coterie does not document OAuth scopes; access is controlled by partner-issued Publishable and Secret API keys passed as a token in the Authorization header, with certain operations requiring the Secret key (https://docs.coterieinsurance.com/#authentication-guide).

📄 Provider scope reference: https://docs.coterieinsurance.com/#authentication-guide

Source

OAuth Scopes

generated: '2026-07-11'
method: derived
source: openapi/coterie-openapi.yml
docs: https://docs.coterieinsurance.com/#authentication-guide
note: Coterie does not document OAuth scopes; access is controlled by partner-issued
  Publishable and Secret API keys passed as a token in the Authorization header,
  with certain operations requiring the Secret key
  (https://docs.coterieinsurance.com/#authentication-guide).
schemes:
- name: oauth2
  source: openapi/coterie-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api.coterieinsurance.com/v1/oauth/token
scopes: []