Connections > Klaviyo connection properties > Connect to Klaviyo

Connect to Klaviyo

Let's configure the Klaviyo connection properties to connect to Klaviyo.

Before you begin

Before you get started, you'll need to get the relevant configuration details from your Xero account based on the authentication type that you want to configure.

Check out Prepare for authentication to learn more about the authentication prerequisites.

Klaviyo connection details

When you create a Klaviyo connection, configure the connection properties.

The following table describes the basic connection properties:

Connection property	Description
Connection Name	Name of the connection. Each connection name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + -, Maximum length is 255 characters.
Description	Description of the connection. Maximum length is 4000 characters.
Use Secret Vault	Stores sensitive credentials for this connection in the secrets manager that is configured for your organization. This property appears only if secrets manager is set up for your organization. This property is not supported by Data Ingestion and Replication and the Data Access Management services. When you enable the secret vault in the connection, you can select the credentials that the Secure Agent retrieves from the secrets manager. If you don't enable this option, the credentials are stored in the repository or on a local Secure Agent, depending on how your organization is configured. Note: If you’re using this connection to apply data access policies through pushdown or proxy services, you cannot use the Secret Vault configuration option. For information about how to configure and use a secrets manager, see "Secrets manager configuration" in the Administrator help.
Runtime Environment	The name of the runtime environment where you want to run tasks. You can specify a Secure Agent or a Hosted Agent.

Authentication types

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

Select the required authentication type, and then configure the authentication-specific parameters.

OAuth 2.0 authorization code authentication

OAuth 2.0 authentication requires the OAuth 2.0 protocol with the Authorization Code grant type to connect to Klaviyo. Authorization code allows authorized access to Klaviyo without the need to share or store your login credentials. This is the default authentication type.

Klaviyo uses the PKCE flow, which requires a unique code_challenge and code_verifier for every authorization request.

The following table describes the connection properties for OAuth 2.0 authorization code authentication:

Property	Description
API Revision Date	The date-based version of the Klaviyo API you want to connect to. Select the revision date to send in the request message header. The default value is the latest stable version.
Authorization URL	The Klaviyo server endpoint that authorizes the user request. The authorization URL is https://www.klaviyo.com/oauth/authorize
Authorization Code Parameters	Additional parameters to use with the authorization URL. You can add multiple parameters, separated by commas, in the following JSON format: [{"Name":"<parameter name>","Value":"<parameter value>"}, {"Name":"<parameter name>","Value":"<parameter value>"}] To securely exchange the authorization code when you connect to Klaviyo, you must define the code_challenge parameter. To specify the hash algorithm that you used to transform the code verifier, you can define the code_challenge_method parameter. For example: [{"Name":"code_challenge","Value":"<parameter value>"},{"Name":"code_challenge_method","Value":"parameter value"}]
Access Token URL	The Klaviyo access token URL that exchanges the authorization code for an access token. The access token URL is https://a.klaviyo.com/oauth/token
Access Token Parameters	Additional parameters to use with the access token URL. You can add multiple parameters, separated by commas, in the following JSON format: [{"Name":"<parameter name>","Value":"<parameter value>"}, {"Name":"<parameter name>","Value":"<parameter value>"}] To securely exchange the authorization code when you connect to Klaviyo, define the code_verifier parameter. For example: [{"Name":"code_verifier","Value":"<parameter value>}]
Client ID	The client identifier issued to the client during the application registration process.
Client Secret	The client secret key issued during the Klaviyo application registration process.
Scope	The scope of the access request. To establish a connection to Klaviyo, you must specify the lists:read scope at a minimum. To add multiple scopes, separate each scope with a space. For example: accounts:read campaigns:read lists:read
Access Token	The access token granted by Klaviyo to access data. Enter an externally generated access token, or click Generate Token to populate the access token.

API key authentication

API key authentication requires a unique API key to connect to the Klaviyo endpoint.

The following table describes the connection properties for API key authentication:

Property	Description
API Revision Date	The date-based version of the Klaviyo API you want to connect to. Select the revision date to send in the request message header. The default value is the latest stable revision date.
API Key	The unique private API key that Klaviyo Connector uses to authenticate API calls made to the Klaviyo endpoint.