I'm using this code to sign up emails that are submitted through a form on our site:
The form is one in the footer here (site is currently in development):
The only thing I changed about the script was that I changed the third parameter of "addContact" to true, so the "action_by" parameter would be "ACTION_BY_VISITOR". For the most part, this form works. It even works when I try to submit an email that's already on the list… except not always. On one email we tested, it returned this error:
Array (  => Array ( [error_key] => http.status.conflict [error_message] => There was a conflict between the supplied data and the existing resource. ) )
I'm happy to send on the full set of data from the Exception object, I just didn't want to paste it here in case it included private data I should post publicly.
I tried searching around the web and this form for answers, but I didn't find any.
Thanks for any help you can provide.
on behalf of the Des Plaines Public Library
Looks like the error is, while not very helpful on detail, telling us that the data supplied is in conflict with the current data on the contact so we couldn't update it. Could you send over the details in an email to our support team so we can look at this specific contact update request and the existing contact? You can email use at webservices[@]constantcontact.com.
Please help in "There was a conflict between the supplied data and the existing resource" error.
I am using constant contact php-api and I am getting the above mentioned error, but it does not occur while creating a new contact while the same error occurs when I am updating a contact (when confirmed opt-in is on he has confirmed the subscription). Also I dont get any error whether it is adding a new contact or updating an existing contact while the Confirmed opt-in is not used. I have already checked the email problem its related to email duplication.Dont know what to do, Please help me.
Posted a response on some of your other posts. This is not related to the original topic but we did mention this defect in our May release notes: http://developer.constantcontact.com/docs/release-notes/may-2014-rel-notes.html. We are working on fixing this defect now and hope to have it in a future release.