Skip to main content
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

​
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:
This is the only callback URL authsome’s PKCE flow listens on. Dashboard: https://www.klaviyo.com/oauth/client.

​
Log in

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 in your vault and reused on every subsequent login. A second browser window then opens to https://www.klaviyo.com/oauth/authorize for the authorization step. Verify:

​
Custom scopes

The bundled definition requests accounts:read. Override at login time:
The granted scopes are stored on the connection and visible in 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.

​
Use the token

Run the agent under the proxy (recommended).
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

User-registered files always win over bundled definitions.

​
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.

OAuth providers

All bundled OAuth providers.