About AnalyticsEdge

My post got banned as SPAM. So putting it here although it might not be 100% related. We are in charge of 20 customer websites. Each customer has a separate (own) account. Around July 1st - July 6th, all websites stopped working with Constant Contact. By that I mean websites will no longer provide new email addresses which we get on Newsletter Sign up form and send them to the proper Constant Contact list. When I go on my server to check to log in with the correct credentials I get this message: Unauthorized - This is an authentication problem. Primary reason is that the API call has either not provided a valid API Key, Account Owner Name and Associated Password or the API call attempted to access a resource (URI) which does not match the same as the Account Owner provided in the login credentials. I then went to Constant Contact to log in with the same credentials and they work.  Please help! ... View more

Thank you for reaching out to Constant Contact API Developer Support. My team is here to assist outside software developers with questions about building into Constant Contact's API.   We’ve recently had some reports of the error “Http.status.bad_request Our service is temporarily down. Please try again later” and are looking into the root cause. What we have found so far is that accounts with special characters in their usernames are affected, while accounts that have strictly alphanumeric usernames will not get this error. Currently the only workaround is to change the affected account’s Constant Contact username in order for the V2 API call to work correctly. https://knowledgebase.constantcontact.com/articles/KnowledgeBase/5889-change-user-name-or-login-name   This error has been submitted for review and investigation by our engineering team. If you have any time stamped logs specific to when this started happening, and/or if you could advise whether/when you were able to make those calls successfully to the affected accounts previously, it may be able to help us narrow down what happened. Your feedback and experience with this defect is essential to improving our product, so thank you for reaching out to us regarding this matter. We look forward to finding the root cause of this issue so that it can be resolved.   Please let us know via email at webservices@constantcontact.com, and reference case number 28489166. ... View more

Thank you for reaching out to Constant Contact API Developer Support. My team is here to assist outside software developers with questions about building into Constant Contact's API.   We’ve recently had some reports of the error “Http.status.bad_request Our service is temporarily down. Please try again later” and are looking into the root cause. What we have found so far is that accounts with special characters in their usernames are affected, while accounts that have strictly alphanumeric usernames will not get this error. Currently the only workaround is to change the affected account’s Constant Contact username in order for the V2 API call to work correctly. https://knowledgebase.constantcontact.com/articles/KnowledgeBase/5889-change-user-name-or-login-name   This error has been submitted for review and investigation by our engineering team. If you have any time stamped logs specific to when this started happening, and/or if you could advise whether/when you were able to make those calls successfully to the affected accounts previously, it may be able to help us narrow down what happened. Your feedback and experience with this defect is essential to improving our product, so thank you for reaching out to us regarding this matter. We look forward to finding the root cause of this issue so that it can be resolved.   Please let us know via email at webservices@constantcontact.com, and reference case number 28489166. ... View more

Hey Jimmy, any news on when Autoresponders will be added to the v3 API now?  A lot of our subscribers are asking this so I thought we should head to the source.  ... View more