Skip to main content

Documentation Index

Fetch the complete documentation index at: https://authsome.agentr.dev/docs/llms.txt

Use this file to discover all available pages before exploring further.

Klaviyo (OAuth) is a bundled OAuth2 provider in authsome. Account-level read access. For full data access against your own account, use the API-key variant (klaviyo).

At a glance

Provider nameklaviyo-oauth
Display nameKlaviyo (OAuth)
Auth typeOAuth2
Default flowpkce, PKCE browser flow
PKCE supportedYes
Device code supportedNo
DCR supportedNo
Default scopesaccounts:read
Proxy hosta.klaviyo.com
Env var (access_token)KLAVIYO_OAUTH_ACCESS_TOKEN
Env var (refresh_token)KLAVIYO_OAUTH_REFRESH_TOKEN
Provider docsLink

Prerequisites

You need to register an OAuth app with Klaviyo (OAuth) once. Klaviyo’s OAuth program is partner-only. Register your app through the Klaviyo developer portal. The redirect URI must be:
http://127.0.0.1:7998/auth/callback/oauth
This is the only callback URL authsome’s PKCE flow listens on. Dashboard: https://www.klaviyo.com/oauth/client.

Log in

uvx authsome login klaviyo-oauth
The first time, authsome opens a local form at http://127.0.0.1:7998 to collect your client_id and client_secret. They are encrypted under your profile and reused on every subsequent login. A second browser window then opens to https://www.klaviyo.com/oauth/authorize for the authorization step. Verify:
uvx authsome get klaviyo-oauth --field status
# → connected

Custom scopes

The bundled definition requests accounts:read. Override at login time:
uvx authsome login klaviyo-oauth --scopes "<comma-separated>"
The granted scopes are stored on the connection and visible in uvx authsome get klaviyo-oauth.

Multiple accounts

Pass --connection <name> on login and on every read command to keep two or more accounts on the same provider side by side. See Multiple connections per provider for the full pattern.
uvx authsome login klaviyo-oauth --connection personal
uvx authsome login klaviyo-oauth --connection work

Use the token

Run the agent under the proxy. The library tab is for embedding authsome inside a larger Python orchestrator.
uvx authsome run -- python my_agent.py
Under the proxy, authsome sets KLAVIYO_OAUTH_ACCESS_TOKEN=authsome-proxy-managed in the child’s environment and injects the real token into outbound requests to a.klaviyo.com. The child process never sees the actual value. Refresh tokens are never exported.

Override the bundled definition

uvx authsome inspect klaviyo-oauth > ~/.authsome/providers/klaviyo-oauth.json
# edit scopes, base_url, or anything else
uvx authsome list   # source now shows "custom" for klaviyo-oauth
User-registered files always win over bundled definitions. See Provider schema.

What’s next

Run agents with the proxy

Inject the access token into outbound requests without exposing it.

Multiple connections per provider

Keep two or more accounts on the same provider side by side.

Provider schema

Every field in a provider definition.

OAuth providers

All bundled OAuth providers.