Skip to main content

Required Klaviyo API permissions for contact syncing with Notify Me

Make sure your Klaviyo API key includes profiles:write access so Notify Me can create and sync contacts successfully.

Updated over a week ago

To successfully sync subscriber data from Notify Me to Klaviyo, your private API key must include the correct permissions. Specifically, it must have the profiles:write scope. Without this, Notify Me cannot create or update contacts in your Klaviyo account.


Why is this important?

Notify Me uses the Klaviyo API to push new subscribers to your Klaviyo account. This enables automated flows, list segmentation, and other contact-based functionality. If your API key does not have permission to write to the Profiles object, contact syncing will fail and your integration will not function as expected.


What happens if the required permission is missing?

If your API key does not include the profiles:write scope:

  • New subscribers from Notify Me will not appear in Klaviyo

  • Automations, segments, and lists that depend on new contacts will not trigger

  • You may see the following error message:

    "Your API key is missing required scopes: profiles:write"

  • The Notify Me to Klaviyo integration will appear to be connected but will not sync contacts


How to update your Klaviyo API key

You can either create a new Full Access API key or a Custom Key with the required scope.

Option 1: Create a Full Access API key

  1. Go to Klaviyo > Account > Settings > API Keys

  2. Click Create Private API Key

  3. Choose Full Access Key

  4. Name your key (e.g. "Notify Me integration")

  5. Click Create

  6. Reconnect your Klaviyo integration in Notify Me using the new key

Option 2: Create a Custom API key with Profiles β†’ Full Access

  1. Go to Klaviyo > Account > Settings > API Keys

  2. Click Create Private API Key

  3. Choose Custom Key

  4. Under the Profiles section, set permission to Full Access

  5. Save your key

  6. Reconnect your Klaviyo integration in Notify Me using the new key


Need help?

If your integration still fails after updating your API key, contact our 24/7 support team.

Did this answer your question?