Skip to main content
Contributor I
October 2, 2025
Solved

Bulk Subscribe Profiles endpoint not creating profiles if not found

  • October 2, 2025
  • 4 replies
  • 180 views

Hi there!

I am using the Bulk Subscribe Profiles API endpoint: https://developers.klaviyo.com/en/reference/bulk_subscribe_profiles

I have noticed that it doesn’t create a profile when subscribing with a person’s email address that doesn’t exist as a Klaviyo profile. The documentation mentions that: If a profile cannot be found matching the given identifier(s), a new profile will be created and then subscribed. I get a 202 status code in my response, but I don't see the person's email address added to my list.

Is there a mistake in my request or is there certain conditions that need to be met to create a profile before subscribing them to a list?


Here is my request:
Request: POST https://a.klaviyo.com/api/profile-subscription-bulk-create-jobs

{
"data": {
"type": "profile-subscription-bulk-create-job",
"attributes": {
"historical_import": false,
"profiles": {
"data": [
{
"attributes": {
"email": "example+123@contact.com",
"subscriptions": {
"email": {
"marketing": {
"consent": "SUBSCRIBED"
}
}
}
},
"type": "profile"
}
]
}
},
"relationships": {
"list": {
"data": {
"type": "list",
"id": "SmXX9X"
}
}
}
}
}

Any insights or examples would be greatly appreciated! Thank you for your help.

Best,
-Amanda

    Best answer by Byrne C

    @amandacub,

    I agree with Cadence’s assessment. If you were running a large amount of tests at once, there’s a chance that these API calls may have brought the attention of our bot detectors. Happy to look into this, but we’d need some specific account information to do this. If you’d like, feel free to DM me privately with your account ID, email address and the approximate date and time you made these API calls, and we can explore this further.

    4 replies

    Kim from Cadence
    Partner
    Partner
    October 2, 2025

    Hey ​@amandacub

    A few questions for you:
    1. Is your list (SmXX9X) a double- or single-opt-in list? If it’s double opt in, this is expected behavior. The profile would have to confirm their subscription in order for the profile to be created and added to the list. 
    2. Are you using the latest revision (2025-07-15), or another one? 
    3. Have you tried using a more realistic email address that you control? It’s possible that klaviyo is filtering this out as a “fake” profile

    Kim — Founder @ Cadence | Helping brands automate recurring campaigns (daily, weekly, monthly) | Happy to connect! | https://cadencecampaigns.com
    amandacubAuthor
    Contributor I
    October 2, 2025

    Hey ​@amandacub

    A few questions for you:
    1. Is your list (SmXX9X) a double- or single-opt-in list? If it’s double opt in, this is expected behavior. The profile would have to confirm their subscription in order for the profile to be created and added to the list. 
    2. Are you using the latest revision (2025-07-15), or another one? 
    3. Have you tried using a more realistic email address that you control? It’s possible that klaviyo is filtering this out as a “fake” profile

    Hi ​@cadence !

    1. My list is a doubt opt in. However, I tested with a single opt in list and saw that the behavior (of not creating profiles) was the same for both single and double opt in lists.
    1. I am using the 2025-04-15 revision.
    2. Yeah, I tested with a valid email address. I didn’t want to include it here so I replaced it in my post.

     

    Kim from Cadence
    Partner
    Partner
    October 7, 2025

    Hey ​@amandacub, thanks for sharing. It’s possible you have run up against Klaviyo’s spam email protections. I’d recommend reaching out to Klaviyo Support and they can help you look into it further.

    Kim — Founder @ Cadence | Helping brands automate recurring campaigns (daily, weekly, monthly) | Happy to connect! | https://cadencecampaigns.com
    Byrne C
    Community Manager
    Byrne CAnswer
    Community Manager
    October 7, 2025

    @amandacub,

    I agree with Cadence’s assessment. If you were running a large amount of tests at once, there’s a chance that these API calls may have brought the attention of our bot detectors. Happy to look into this, but we’d need some specific account information to do this. If you’d like, feel free to DM me privately with your account ID, email address and the approximate date and time you made these API calls, and we can explore this further.