Manage OAuth providers for end-user authentication (configure, get, update, delete).
Actions:
- "configure": Set up a new OAuth provider (idempotent upsert)
- "get": Read provider config (single provider or all). client_secret is redacted.
- "update": Patch existing provider — only supplied fields change
- "delete": Remove a provider. Existing sessions remain valid until expiry.
Built-in providers (URLs/scopes auto-filled — only client_id, client_secret, redirect_uris required):
google, github, discord, facebook, linkedin, microsoft, apple, x
For any other provider name, supply authorization_url, token_url, userinfo_url manually.
Parameters by action:
configure: { app_id, action: "configure", provider, client_id, client_secret, redirect_uris, scopes?, authorization_url?, token_url?, userinfo_url?, provider_metadata? }
get: { app_id, action: "get", provider? } // omit provider to list all
update: { app_id, action: "update", provider, ...fields-to-change }
delete: { app_id, action: "delete", provider }
Example — configure (Google):
Input: { app_id: "app_abc123", action: "configure", provider: "google",
client_id: "...", client_secret: "GOCSPX-...",
redirect_uris: ["https://api.butterbase.ai/auth/app_abc123/oauth/google/callback"] }
Example — configure (Apple, requires provider_metadata):
Input: { ..., provider: "apple", provider_metadata: { teamId, keyId, privateKey } }
Provider notes:
- X (Twitter): no email — synthetic {username}@users.noreply.x.local is used
- Apple: only returns name on first auth; uses POST callback (handled automatically); requires provider_metadata { teamId, keyId, privateKey }
- Facebook: default scopes email, public_profile
OAuth flow after configure:
GET {api_base}/auth/{app_id}/oauth/{provider}?redirect_to=https://yourapp.com/auth/callback
After successful authentication, user is redirected to redirect_to with tokens as query params.
Common errors:
- RESOURCE_NOT_FOUND: app or provider doesn't exist
- VALIDATION_INVALID_SCHEMA: empty client_id/client_secret, or invalid URL on a custom provider
Idempotency: configure/update/delete are safe to retry.
Warning (delete): prevents future sign-ins via that provider; existing sessions remain valid until they expire.