Prepare for authentication

You can configure the OAuth 2.0 authorization code or API key authentication types to access Klaviyo.

Before you configure the connection properties, you need to keep the authentication details handy based on the authentication type that you want to use.

To connect to Klaviyo using the OAuth 2.0 authorization code, you need the API revision, authorization URL, access token URL, client ID, client secret, authorization code parameters, access token parameters, and scope.

Before you configure the connection, create a public OAuth app in Klaviyo and register the following Informatica redirect URI:

Klaviyo uses the Proof Key for Code Exchange (PKCE) flow, which requires specific parameters for every authorization request. Generate a unique code_challenge and code_verifier to pass to the authorization code and access token parameters.

For more information about how to create a public OAuth app and set up the PKCE flow, see Create a public OAuth app and Make API calls using OAuth in the Klaviyo documentation.

To connect to Klaviyo using API key authentication, you need a unique API key that Klaviyo Connector uses to authenticate the API calls made to the Klaviyo endpoint.

When you create the private API key in Klaviyo, grant read access to the Lists scope. You need the Lists scope to test the connection.

For more information about how to generate and use an API key, see Authentication API Requests in the Klaviyo documentation.