About Mark-C

Hello,   A 403 response can be returned if the the non-SSL version of the request uri is used (i.e., http://... should be https://..), or if the resources being accessed are for an account other than the one authorized through your authentication process.     The link attribute you provided appears to be for the lists collection (the list of contact lists in the account), rather than a specific list, as well.  Is the list creation where you're getting the 403 response?  ... View more

Hello,   I assume you are referring to our PHP Wrapper Library.  Regardless, in our data model, interest/lists are attributes of the contact, so to unsubscribe a contact from a single list, you would need a to make up to three API calls, depending on whether you already have the contact details including the contacts ID on hand for your application's use.   The flow would be something like this:   1) Search for the contact by email address (makes a GET request specifying an email address). 2) If a contact with this email address is found, use the returned ID to retrieve the contact's information (GET request that returns full details for the contact, including current ContactLists attributes for the contact). 3) Remove just the list you wish to unsubscribe the contact from from the the contactlists that are returned in the contact object, and then update the contact (makes a PUT request to update the contact, which will replace current contact details with the new modified details.   I hope this helps. Let us know if you have additional questions. ... View more

Hello,   I've edited your post to remove any private information (email addressed, account credentials) for your security. ... View more

Hello,   In order to add a second list/interest attribute to an existing contact in an account, you need to submit the API request to update the contact with both the old and the new lists included in your request. Updating contacts through the API replaces current information with new information provided.   The behavior you're seeing is typically caused by the second request including only the new list you wish to add the contact to, which replaces the previous list.    I hope this helps you get things working as you would like. Let us know if you have additional questions.         ... View more

Hello,   In your script, is $tmpfile a file handle for a temporary file, or is the XML string going directly into the $tmpfile string?  If the latter, this typically doesn't work with PHP cURL PUT requests, and I confirmed our API will return the 400 error you repoted.   The XML you are using is fine, based on my testing, but your request code may need a little tweaking. I was able to get the request to fly in in my test account by first putting xml into the string $entry, and writing it to a temporary file ($tmpfile) using the tmpfile() function, so instead of a string variable, $tmpfile is actual the handle for the temporary file. For convenience, I also made a small change to how the CURLOPT_USERPWD is set up in your code, resulting in the following working example:   <?php $entry = 'THE_XML'; $tmpfile = tmpfile(); fwrite($tmpfile, $entry); fseek($tmpfile, 0); // Put your API Key, Username and Password here $auth = $API_Key."%".$username.":".$password; // Initialize the curl session $request ="https://api.constantcontact.com/ws/customers/{username}/contacts/{user ID}"; $session = curl_init($request); curl_setopt($session, CURLOPT_USERPWD, $auth); curl_setopt($session, CURLOPT_HTTPAUTH, CURLAUTH_BASIC); curl_setopt($session, CURLOPT_INFILE, $tmpfile); curl_setopt($session, CURLOPT_PUT, 1); curl_setopt($session, CURLOPT_INFILESIZE, strlen($entry)); curl_setopt($session, CURLOPT_HTTPHEADER, Array("Content-Type:application/atom+xml")); curl_setopt($session, CURLOPT_HEADER, false); // Do not return headers curl_setopt($session, CURLOPT_RETURNTRANSFER, 0); curl_setopt($session, CURLOPT_SSL_VERIFYPEER, 0); $response = curl_exec($session); $httpcode = curl_getinfo($session, CURLINFO_HTTP_CODE); curl_close($session); ?>  I hope this helps you get your PUT requests rolling.   Cheers, ... View more

Hello,   I just used the XML you provided to successfully update a contact in a test account using a PUT request. Did you recieve the error with the XML while making a request to update this contact (say, to make changes or add list memberships to the contact record? ... View more

Hi Ken,   The python library was put out as open source and unsupported by Constant Contact Labs, but regardless I'm happy to help try and diagnose the issues using RESTClient (which you can also do)... Unfortunately, I've identified an inconsistency in repsonses to the same request that indicates we may be having an issue with our API Services at this time. I hope to have more to report on this by later this evening, but at this hour, I may not have moreuntil the morning. ... View more

Hello,    Any number of Constant Ccontact accounts can authenticat using a single application's API Key. The redirect uri is part of the OAuth 2 flow, in which a script you hose handles the redirect/callback, and passed the credentials on to the client, and is the approach I would recommend.    We have implemented a client flow, which is partly detailed at the bottom of our OAuth 2 documentation, and this can handled via javascript on a static pages you host, and then set the access token returned with the client (I am planning to post an example client flow javascript snippet soon). In this case, you just need to have one script that all clients authenticate through (using your API Key and their login credentials), which plants a the access token cookie with the client. Note that the one thing missing from our OAuth 2 documentation at present, is the request needed to retrieve the username after the acces token is obtained.   I hope this is helpful.  The redirect uri being specified in the API key settings is part  of the OAuth 2 standards, and is designed to prevent redirect exploits. At this time, we aren't implementing a desktop application flow.   You could choose to use OAuth 1.0a, for which we have a Out of Band (oob) desktop application flow, that doesn't require a staticuri, but OAuth 1.0 is programmatically more difficult to implement and troubleshoot, so I would really recommend adapting an OAuth 2 client flow strategy. ... View more

Hello,   Is this result the same for every contact email you search? Please contact me via email (webservices@constantcontact.com). In the email, if you can provide the username for the Constant Contact account and one or a small number of email addresses you're using with the search method, I'll see if I can get a test set up with that information, as this may clearly be an issue with the wrapper library.   Thanks in advance. ... View more

Hello Scott,   Because of the way documents are filed and stored on our system when uploading, and having no API functionality for retrieving document lists or information to facilitate getting the lists url's it would be difficult to use our library to host the invoices for your purposes. Further, account libraries are limted to 50 MB combined space for images and documents, so the number of invoices you would be able to handle this way would be limited.   I would suggest hosting your invoices on your own server or webhost in a static "current invoices" folder or directory. This way, the only thing different among your customers could be the filenames, and a variation on the approach outlined above for dynamic customer-specific links would be applicable. If you provide a static name for current invoice for each customer, you may be able get away with setting the custom fields used for the dynamic link once, so that your monthly email would simply contain a "current invoice" link, and you wouldn't need to update your contacts each month with new data for the custom fields before sending your emails.   I hope the above is helpful.   Cheers,   ... View more

Hello Mary,   You're quite welcome, and I'm happy to hear that.  I used REST Client to troubleshoot your XML.  I highly recommend as a troubleshooting tool for REST API requests.  You can find information on setup and use at the link above. ... View more

If you are using the bulk API, your contacts will be updated with the new information submitted in your request, and you won't have a per-contact response to tell you whether the contact was present alredy present.  You could request list members or active contacts before your request to add/update via the bulk activities API and cross-reference locally, however.     If you are syncing or adding small numbers of contacts in a given event, no more than 25 contacts per sync as per our API Terms of Service to preserve quality of service, using a POST request to add the contacts would create contacts if they are not already on a list in the account, or return a 409 Conflict if the email address in a request is already present in the account.  In this case, the contact will not be udpated with the new information.  If you use PUT method for the same request  instead, the contact would simply be updated. ... View more