OAuth providers - Authsome

Authsome ships with 14 bundled OAuth2 providers. Each has a default flow (PKCE, device code, or Dynamic Client Registration) and a api_url for proxy injection. You can override any of them by dropping a JSON file with the same name into ~/.authsome/providers/.

Bundled OAuth providers

Provider	Flow	Host	Notes
atlassian	`pkce`	`api.atlassian.com`	Jira and Confluence Cloud.
discord	`pkce`	`discord.com`	Bot and user OAuth.
github	`pkce`	`api.github.com`	Device code also supported.
gitlab	`pkce`	`gitlab.com`	Self-hosted via `--base-url`.
google	`pkce`	`regex:.googleapis.`	Covers Gmail, Drive, Calendar, etc.
hubspot	`pkce`	`api.hubapi.com`
klaviyo-oauth	`pkce`	`a.klaviyo.com`	OAuth variant. The API-key variant is `klaviyo`.
linear	`pkce`	`regex:.*\.linear\.app`	Standard OAuth app.
microsoft	`pkce`	`graph.microsoft.com`	Microsoft Graph.
notion	`pkce`	`api.notion.com`	Standard OAuth app.
notion_dcr	`dcr_pkce`	`mcp.notion.com`	DCR variant of Notion via the MCP endpoint.
postiz	`device_code`	`api.postiz.com`	Headless-friendly.
slack	`pkce`	`slack.com`	Workspace-scoped.
x	`pkce`	`api.twitter.com`	X (formerly Twitter).

For all providers in one CLI view:

authsome list

How the bundled flow is chosen

Every provider definition declares a default flow. The four flow types:

Flow	When
`pkce`	Standard OAuth2 with PKCE. Browser-capable setup. Requires registering an OAuth app at the provider.
`device_code`	Headless OAuth2. User enters a code on a separate device. No callback URL to register.
`dcr_pkce`	Dynamic Client Registration followed by PKCE. The provider registers an OAuth client for you. Used for services that support DCR.
`api_key`	Not OAuth. See API-key providers.

Override the flow at login time if the provider supports the alternative:

authsome login github --flow device_code

Add an OAuth provider

If authsome doesn’t bundle the provider you need:

Find the provider’s authorization_url, token_url, and supported scopes.
Write a JSON definition. See Custom providers for templates.
authsome register ./<name>.json.

What’s next

Log in with OAuth

The full OAuth login walkthrough.

API-key providers

The other half of the bundled set.

Custom providers

Add an OAuth provider authsome doesn’t ship.

Provider registry

How authsome resolves names to definitions.

​Bundled OAuth providers

​How the bundled flow is chosen

​Add an OAuth provider

​What’s next