How to Manage Your Account's API Keys

Last updated at:


As you look to leverage Klaviyo's API or integrate with other third-party tools, you will need to know where to find your 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

To access and manage your account's API Keys, click the account dropdown in the upper right and select Account.


Then, select SettingsAPI Keys.


View both your public API key (i.e., Site ID) and your private API keys in this location.


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


You may wish to label each private API key for clarity. To do so, select the pencil icon next to the private API key name. A window will appear where you can type in a new label. Then, select Save API Key.


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 as well as an API key used to integrate with a shipping or help desk application.

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


Additional Resources

Was this article helpful?
347 out of 587 found this helpful