Hi @Steven!

A 202 response doesn’t always indicate list-bombing - in fact, that’s a less common reason for that status code to appear.

Per our guide on rate limits, status codes, and errors, a 202 status code just means that the action requested in the API call occurs asynchronously - which is normal for a list that has double opt-in enabled (the subscribe cannot be performed until the recipient completes the opt-in).

I hope this helps!

- Brian

Hi Brian, that makes sense. Thank you for the answer. Since the profiles are not being added to the list I am attempting to subscribe them to (and when I test it with my own email, the double opt-in never gets sent), is there any other action I need to take beyond hitting this endpoint to get the emails to start getting added to the list?

Thanks,

Hi Brian, was there any additional thoughts here? We are hitting the above endpoint, getting a 202, but the double opt in email never gets sent.

Hi @Steven!

Have you checked the Spam folder of your email that you’re testing with? If you’re not receiving the opt-in email at all, it’s possible that your inbox provider is filtering it out. 

Best,
Brian