Below is the XML i'm PUTing to update a contact to be included in contact lists. The lists are included in the account owners sign up form and everything is working as expected...
Apart from the OptInSource tag. I'm setting this to ACTION_BY_CONTACT because users are can opt themselves back in to the lists using the a web form. Even though I'm setting the tag to ACTION_BY_CONTACT the emails always appear in the lists as 'Added by Site owner'. New contacts are shown as 'Added by Contact'.
Can you offer some advice please? Is it impossible to add ACTION_BY_CONTACT updates to contacts through the API? As you can see I've tried adding the OptInSource in the ContactList tags also but with no joy.
Many thanks for any help you can provide.
<title type="text">Contact: </title>
<Contact xmlns="http://ws.constantcontact.com/ns/1.0/" id="http://api.constantcontact.com/ws/customers//contacts/892">
<link xmlns="http://www.w3.org/2005/Atom" href="http://api.constantcontact.com/ws/customers//lists/25" rel="self"></link>
<link xmlns="http://www.w3.org/2005/Atom" href="http://api.constantcontact.com/ws/customers//lists/24" rel="self"></link>
Has this been resolved?
Also what happened to the workaround docs at the link above: http://developer.constantcontact.com/doc/siteVisitorAPI
The documentation posted at http://developer.constantcontact.com/doc/siteVisitorAPI is still active, but you would need to be logged into the site to view this documentation. Please note as the documentation states, that while the Site Visitor API still functions, it is being deprecated shortly. We would strongly recommend that you take a look at using our Rest API which has increased functionality and is the preferred method for future development. If you are still experiencing issues accessing the documentation above after logging into this site with your developer login, please let us know. Thanks.
It is worth noting, this issue has been resolved and the workaround is not needed. Contacts added to the Do Not Mail list can again be added back into an account with the REST API. Please note: it is a violation of the Constant Contact Terms and Conditions and the Constant Contact API Terms and Conditions to add back any contact who has not explicitely taken action to be added back. Please see our T&C for more detailed information regarding this.
Sorry for the confusion with that link. Our siteVisitorAPI is a depricated API feature which is no longer given out to any new or existing customers. Our REST API has both replaced all the functionality of that API and augmented it with more control, features and usability. The documentation link is no longer available to any of our customers going forward and this API will, at some point, be completely phased out requiring anyone who is currently implementing it to change over to our REST API. That date is not determined yet and will be given plenty of lead time for adjustments when it is determined.
Regarding the issues with PHP servers and cURL, we have done extensive testing in numberous hosting, OS and PHP/cURL version environments and have as yet been unable to replicate any of these problems in these environments. Many of our testing environments are outside of Constant Contact using popular hosting companies to ensure that our sample code works in these environments.
From all indications of the issues, the problem does appear to be around server settings rather than code issues. Since many customers are able to use it in local test environments or prior to updating server configurations or packages, this is a definitive indicator that the issue is caused by said server configurations or packages and not by the code itself. We are happy to look into these issues as best we can, however server environments are often very difficult to troubleshoot. Please send any additional information you have to the email address Dave J mentioned in his above post if you would like us to assist you further. It will be best to have more information about your server and OS configurations included as well to see if we can find an issue with the configuration.