Butterbase Ai Authentication

generated: '2026-11-03'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://docs.butterbase.ai/core-concepts/authentication/
sources:
- https://docs.butterbase.ai/core-concepts/authentication/
- https://docs.butterbase.ai/api-reference/auth-api/
- https://docs.butterbase.ai/getting-started/agents-quickstart/
- https://docs.butterbase.ai/getting-started/before-you-start/
description: Butterbase authentication uses JWT bearer tokens for API calls and OAuth2 for social sign‑in.
schemes:
- type: http-bearer
  name: JWT access token
  evidence: The access token is what your frontend sends with API requests.
  location: header
  header: Authorization
  how_to_obtain: Obtain via POST /auth/{app_id}/login, POST /auth/{app_id}/magic-link/verify, or other auth endpoints which return an "access_token".
- type: oauth2
  name: Social sign‑in (OAuth)
  evidence: Direct the user’s browser to /auth/{app_id}/oauth/{provider}?redirect_to=https://yourapp.com/callback
  location: header
  header: Authorization
  token_url: /auth/{app_id}/oauth/{provider}/callback
  authorize_url: /auth/{app_id}/oauth/{provider}
  scopes:
  - 'google: openid, email, profile'
  - 'github: user:email'
  - 'discord: identify, email'
  - 'facebook: email, public_profile'
  - 'linkedin: openid, profile, email'
  - 'microsoft: openid, email, profile, User.Read'
  - 'apple: name, email'
  - 'x: tweet.read, users.read'
  how_to_obtain: Configure a provider via the OAuth configuration API or MCP tool, then start the flow by redirecting the user to the authorize
    URL; the provider redirects back to the callback URL with an authorization code which is exchanged for tokens.
docs: https://docs.butterbase.ai/core-concepts/authentication/