> For the complete documentation index, see [llms.txt](https://claimlane-docs.gitbook.io/claimlane-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://claimlane-docs.gitbook.io/claimlane-docs/troubleshooting-and-faqs/guide-for-klaviyo-integration-create-profile.md).

# Guide for Klaviyo Integration (Create profile)

#### Step 1: Create a Private API Key in Klaviyo

1. Log in to your Klaviyo account.
2. Click your **account name**.
3. Go to **Settings → API Keys**.
4. Under **Private API Keys**, click **Create Private API Key**.
5. Give the key a recognizable name, e.g., `Integration with Claimlane`.
6. Set the **Access Level** for each scope as shown below.

#### Step 2: Configure the Required Scopes

When creating the key, make sure to set the following scopes:

| Scope             | Access Type | Description                                              |
| ----------------- | ----------- | -------------------------------------------------------- |
| **List**          | Full Access | Allows adding new profiles to a list.                    |
| **Profiles**      | Full Access | Required to create and update profiles.                  |
| **Subscriptions** | Full Access | Enables managing email and SMS subscription preferences. |

Your configuration should look like this:

<figure><img src="/files/rZcj3CNMZrA2mkFLuXdq" alt=""><figcaption></figcaption></figure>

#### Step 3: Copy Your Private API Key

After saving the key:

1. Copy the **Private API Key**.
2. Send it to your contact in Claimlane.

{% hint style="info" %}
**Tips**

* Keep your private key secure, **never share it publicly**.
* You can always revoke or regenerate the key in Klaviyo if needed.
* Only **Private API Keys** support these granular access scopes. **Public keys will not work** for this integration.
  {% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://claimlane-docs.gitbook.io/claimlane-docs/troubleshooting-and-faqs/guide-for-klaviyo-integration-create-profile.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.