180 Insurance · Authentication Profile

180 Insurance Authentication

Authentication

The 180 Seguros Sagas API is protected with OAuth2 using the client-credentials (machine-to-machine) grant, brokered by an Auth0 tenant. Clients exchange a client_id + client_secret for a bearer access token (default lifetime 43,200s / 12 hours) and send it on every request as `Authorization: Bearer {access_token}`. The docs advise reusing tokens while valid rather than minting a new one per call.

180 Insurance secures its APIs with oauth2 across 1 declared security scheme, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the clientCredentials flow(s).

CompanyInsurtechInsuranceEmbedded InsuranceBrazilFintechAPIWebhooks

Methods: oauth2 Schemes: 1 OAuth flows: clientCredentials API key in:

Security Schemes

OAuth2ClientCredentials oauth2

Source

Authentication Profile

generated: '2026-07-17'
method: searched
source: https://docs.180s.com.br/reference/autenticacao
docs: https://docs.180s.com.br/reference/autenticacao
summary:
  types: [oauth2]
  oauth2_flows: [clientCredentials]
  token_auth_methods: [client_secret_basic, client_secret_post, private_key_jwt]
  identity_provider: Auth0
description: >-
  The 180 Seguros Sagas API is protected with OAuth2 using the client-credentials
  (machine-to-machine) grant, brokered by an Auth0 tenant. Clients exchange a
  client_id + client_secret for a bearer access token (default lifetime 43,200s /
  12 hours) and send it on every request as `Authorization: Bearer {access_token}`.
  The docs advise reusing tokens while valid rather than minting a new one per call.
schemes:
- name: OAuth2ClientCredentials
  type: oauth2
  flow: clientCredentials
  token_url: https://180s-staging.us.auth0.com/oauth/token
  grant_type: client_credentials
  token_lifetime_seconds: 43200
  bearer_header: 'Authorization: Bearer {access_token}'
  sources: [docs.180s.com.br/reference/autenticacao, well-known/180-insurance-oauth-authorization-server.json]
notes: >-
  No granular API scope surface is documented — access is scoped per M2M client /
  distribution channel at grant time rather than via request scopes, so no
  scopes/ artifact is emitted. The Auth0 tenant advertises the standard OIDC
  scopes only (openid/profile/email/...), which apply to interactive flows, not
  the API's client-credentials grant.