Brinqa Authentication

generated: '2026-07-18'
method: searched
source: https://docs.brinqa.com/docs/brinqa-api
docs: https://docs.brinqa.com/docs/brinqa-api
summary:
  types: [http]
  http_schemes: [bearer]
  api_key_in: []
  oauth2_flows: []
  notes: >-
    The Brinqa Platform API uses bearer token authentication. A caller first
    obtains an access token by POSTing credentials to the platform's login
    endpoint, then presents the token as an Authorization: Bearer header on
    subsequent GraphQL requests. Multi-factor authentication (MFA) is supported
    during token generation. Tokens are valid for 86400 seconds (24 hours).
schemes:
  - name: bearerAuth
    type: http
    scheme: bearer
    bearerFormat: JWT
    description: >-
      Bearer access token obtained by POSTing user credentials to
      https://<your-brinqa-platform-url>/api/auth/login. Presented as
      "Authorization: Bearer <token>" on GraphQL requests to
      https://<your-brinqa-platform-url>/graphql/caasm.
    token_endpoint: https://<your-brinqa-platform-url>/api/auth/login
    token_lifetime_seconds: 86400
    mfa_supported: true
    sources: [docs.brinqa.com/docs/brinqa-api]
notes: >-
  Brinqa is deployed per-tenant, so the token and GraphQL endpoints are relative
  to each customer's platform URL rather than a single shared host. No OAuth2 /
  OpenID Connect authorization-server metadata is published; there is no OAuth
  scope surface (bearer-token model), so no scopes/ artifact is emitted.