Parafin Authentication

generated: '2026-07-20'
method: searched
source: https://github.com/buildparafin/embedded-demo
docs: https://docs.parafin.com/
description: >-
  Parafin's API uses OAuth 2.0 client-credentials: a platform authenticates with
  its client credentials to redeem a short-lived bearer token, which is then
  used as a Bearer Authorization header on API calls and to initialize the
  embedded Parafin Elements widgets. The public embedded-demo implements a
  server-side proxy so client credentials never reach the browser — the backend
  exchanges credentials and hands the browser only a per-person, per-product
  short-lived token. The docs are login-gated so the full securityScheme detail
  is not machine-verifiable; this profile is derived from the public demo and the
  OAuth server metadata advertised on the docs host.
summary:
  types: [oauth2, http-bearer]
  oauth2_flows: [clientCredentials]
  token_style: short-lived bearer
schemes:
  - name: OAuth2ClientCredentials
    type: oauth2
    flow: clientCredentials
    token_operation: POST /v1/auth/redeem_token
    description: >-
      Platform client credentials are exchanged for a short-lived bearer token
      via POST /v1/auth/redeem_token; the token authorizes API calls and widget
      initialization.
    sources: [https://github.com/buildparafin/embedded-demo]
  - name: BearerAuth
    type: http
    scheme: bearer
    description: Redeemed bearer token presented in the Authorization header.
    sources: [https://github.com/buildparafin/embedded-demo]