Manage Your Account's API Keys

read
Last updated at:

Overview

As you look to leverage Klaviyo's API, or integrate Klaviyo with other third-party tools, you will need to know where to find your Klaviyo account's API Keys. 

Every individual Klaviyo account has one Public API Key which is also called your Site ID. This public key is a unique identifier for your Klaviyo account.  In contrast, a Klaviyo account can generate multiple private API keys as needed.

Find your API Keys

You can access and manage your account's API Keys in your Account Settings.

Navigate to Account Settings by clicking the account name at the upper right corner of your Klaviyo account. Then, in the Settings dropdown, choose API Keys.
API_Key_1_blurred.gif

View both your Public API Key - Site ID and your Private API Keys in this location.
2017-06-01_17-59-58.png

Your Public API Key - Site ID

Your Public API Key is also called your Site ID. This is a short alphanumeric value. Note that there is only one Site ID for each individual Klaviyo account.

Find_Site_ID.png

It is safe to expose your Public API Key, as this key cannot be used to access data in your Klaviyo account.

Your Private API Keys

Private API keys are used for reading data from Klaviyo and manipulating some sensitive objects such as lists.

Treat Private API keys like passwords, kept in a safe place and never exposed to the public.

There may be multiple Private API Keys associated with an individual Klaviyo account.

Find_Public_API_Keys.png

You may wish to label each Private API key for clarity.
Label_API_Key.gif

Generate a Private API Key

You can generate new Private API Keys for different application uses. This can help trace the source of data being added to your Klaviyo account via the API. For example, you may have an API key used to integrate with your eCommerce platform, and an API Key used to integrate with a shipping or helpdesk application.

Within API Settings, click Create an API Key.  Then type in a label for the new API key.

API_Key_2_blurred.gif

x
Was this article helpful?
89 out of 129 found this helpful