Sorry for the delay on our response. We're working on looking through the info you brought up - there does seem to be a little bit of a discrepency here, or at least some clarifications we can make in the documentation. We'll get back to you soon on this. ... View more

Hi James,   It sounds like you are using the Wordpress plugin found here? Unfortunately, we did not develop this plugin, so we probably won't be able to help much with debugging it. I would suggest visiting the Marketplace page for the developer's contact info.   A suggestion that we have made in the past for apps like this is ensuring that you're keeping your username and password up to date in the app. One password change can desync any app and cause issues. ... View more

Hello,   The readme is correct in saying that ctct.dll is required in your program.  You don't actually have the dll, but by building the project you will have it. The project output produces the dll.   I hope that helps. Thanks! ... View more

It looks like you're taking things just one step farther than what the SDK needs. In Mashery, on your API Keys page, you will need to grab the API Key and Redirect URI, and set these as the values in the config file. Then, you will need to set the username and password of the account you are needing to access in the password and username value fields. The application will generate its own access token to use.   I hope this helps - let us know! ... View more

I'd like to know specifically which pieces of sample code you are using, as well as when you started to develop with us. Within the last few weeks, we have moved our API key generator to our V2 API, and these new keys will not work with the V1 endpoints. Also, we have updated our sample code to include the V2 API, and these samples no longer use the CC_Utility class.   Also, when you access one of the endpoints for v1 (example: /ws/customers/username/contacts), to log in via the browser, the format must be as below, but will only work if you have a V1 API key. user: apikey%username password: password I would suggest taking a look at our new sample code page or any of our V2 wrappers in our Github repo if you are just getting started. If you started development in our V1 API before we launched V2 earlier this month, we can definitely still help you with the V1 code and calls. If so, just send an email to webservices@constantcontact.com with the code you are using, including your changes for authentication, and we can take a look at what is preventing authentication. ... View more

A 415 error typically comes from an invalid content-type header, or not setting one. You'll need to set it as Content-type: application/atom+xml  If you currently have that set, just let us know, and we can take a deeper look. ... View more

Yes, any contact that is on the removed list can be placed back on a list easily. ... View more

Hi Doug,   We won't be able to gaurantee a fix, but you're more than welcome to provide your code, and we can take a look. I'd suggest emailing it to us, for privacy reasons. ... View more

Hi Hema,   Currently, a contact cannot be created without adding it to a list. However, if you remove the contact from the list, it will be moved to a "removed" status. This means that the contact's history will stay in your account, but it will not count towards the Active Contact count that goes towards your billing amount. ... View more

Hi David,   It looks like we have some typos in that documentation page. I'll make sure to get them fixed - you'll want to use "EMAIL ADDRESS" for email. We use "POSTAL CODE" for zip code, to make it work for Canada and other international addresses. ... View more

Hi Doug,   I noticed in your first post that you mentioned you had the Content-type header set correctly, but the only way I can replicate the same 415 error is if the header is not present. Would you be able to try the call out using RESTClient? If you're still getting the same error, please save the request/response archive (from the file menu), and send that file to us at webservices@constantcontact.com for a closer look. ... View more

I would suggest using our PHP Wrapper to make this easier. You can the repo on Github here. There are a few different functions for list management that the wrapper uses, and the documentation for them is here. With this wrapper, you'll be able to use whatever details from the list that you need. ... View more

Hi Shane,   There are a few formatting problems with the XML that will cause it to give a 400. When creating a contact, you don't need to pass an ID, as the system will create one for you. You also need to specify at least one list to add the contact to. Here is a snippet of XML that should work for you.   <entry xmlns="http://www.w3.org/2005/Atom"> <title type="text">entry</title> <updated>2008-07-23T14:21:06.407Z</updated> <author></author> <id>data:,none</id> <summary type="text">Contact</summary> <content type="application/vnd.ctct+xml"> <Contact xmlns="http://ws.constantcontact.com/ns/1.0/"> <EmailAddress>test@test.com</EmailAddress> <OptInSource>ACTION_BY_CONTACT</OptInSource> <ContactLists> <ContactList id="http://api.constantcontact.com/ws/customers/{username}/lists/1" /> </ContactLists> </Contact> </content> </entry>   ... View more

Hi Molly,   What action are you trying to complete with this XML? Are you attempting to create a new contact or update an existing one?   Thanks, ... View more

Hi Jason,   I think the issue might be coming from how you are using getContactDetails(). That function is expecting a contact ID, not a contact email address. I would suggest running the email through searchContactsByEmail() first, like this:   $search = $ConstantContact->searchContactsByEmail($email); $Contact = $ConstantContact->getContactDetails($search[0]);  If this is what you are doing, or if this doesn't help, please let us know! ... View more

Hey Josh,   Usually when uploading that number of contacts into your account, we suggest using the bulk load API requests, as it causes a little less strain on our system. Our NOC team may have seen this as an extra load on our system. If you email us at webservices@constantcontact.com with your API key, we can see what happened and get you re-enabled in no time. Sorry for the trouble! ... View more

That's not a problem. You'll want to use the "sends" events from the campaign. If you have preformed any resends to existing contacts, you will need to de-dup the results, but you can access a full list of the recipients from this URI:   /ws/customers/username/campaigns/campaignid/events/sends  This will return the contact's email, a link to the contact, and a timestamp. Hope that helps! ... View more

Hey Andrew,   Clicks act a little differently than other campaign events. We're planning on having an easier endpoint with the next version of our API, but the current version requires clicks to be accessed through the urls inside of the events. You will also need the ID of the URL that you want to gather clicks from, which can be obtained from the campaign resource.   For example, if the campaign ID is "123" and the URL ID is "456", the URI would be built like this: /ws/customers/username/campaigns/123/events/urls/456/clicks  Hope this helps - let me know if you have any questions. ... View more

Hi bssa,   The downloadable version of the CCSFG does not allow any existing contacts to be updated, due to security reasons. If you would like the update version, please read this forum post explaining the risks. Once you have read that post, and understand the risks, email us at webservices@constantcontact.com, and we can send you the update version of the tool. ... View more

Hey Gary,   The detailed clicks can be found by accessing the specific URL's ID from the Campaign resource, using the "Url" node inside of the "Urls" field. The detailed information from this URI will list the time of each click, and the contact that clicked.   Let me know if you have any other questions on this. Thanks! ... View more

Hi Nab,   We still haven't been able to get work started on the update to the C# Library. The bounce links issue is currently being worked on - I'll be sure to update you when it has been resolved. Sorry for the delay. ... View more

Hey Nab,   That's actually something on the back-end of the API that we're looking at getting fixed. Next links (specifically for bounces) are not returning proper results right now. The engineers are taking a look into it, and we'll post an update to the forum when a fix is deployed. Sorry about that!   ... View more

Hi Nabeel,   This is definitely possible, but the functionality doesn't currently exist in the .NET library. We'll start some work on getting this implemented, but unfortunately this is on our backlog, so I'm not expecting this to be available for some time. If you follow the project on github, you can be notified the next time we push updates to the code. ... View more

Hey Brian,   The specific portion of this XML that is giving the error is a small mismatch in your contact ID's. The first link and ID in your PUT XML is directed to /contacts/1, and the rest of the XML is directed to /contacts/5. I've tested your XML using these changes, and things are working on my end. If you're still having issues, just reply back and we'll help however we can! ... View more