I’m hoping someone can shed some light into an odd behaviour I’m seeing.
Adding subscribers to a list using the
/profile-subscription-bulk-create-jobs endpoint is working partially if we make the request on a machine locally or an AWS lambda, but not on a long running node server hosted on heroku.
By partially I mean that we get the 202 acknowledgement, but do not see any double opt-in confirmation emails issued.
If I supply a profile id which should have had a double opt in email sent, would it be possible to confirm whether the IP address matching the API request was indeed blocked?
Best answer by David ToView original