Hello @Mike_Cravitz,   Thank you for reaching out to Constant Contact's API Support.   If this error just started recently then the most likely cause is Mashery is now blocking none TLS 1.2 traffic. We made an announcement back in August regarding this. Please check out the forum post we made regarding this change.   https://community.constantcontact.com/t5/Developer-Support-ask-questions/Support-Ending-for-TLS-v1-0-and-v1-1-Immediate-Action-Required/m-p/319360/highlight/true#M11304 ... View more

Hello @Happiness,   THank you for reaching out to Constant Contact's API Support.   The Contact Form 7 Integration is created by Contact Form 7 themselves and so the support we can provide is extremely limited. If you have already connected the integration to your Constant Contact account that is about as far as I could go. Any other set up would be beyond what our knowledge of the integration entails.   You can check on their website for support information. https://contactform7.com/docs/   You can also look in the upper right of that website for a link to their support forums to post a question or read questions by other users. Perhaps your question has already been answered. I did try to find the specific steps to select a list, but I was not able to find them. ... View more

@Fetzer,   You can do a PUT to update the deleted contact. You would just need to ensure you use the  "update_source": "Contact" to tell the system that the contact is taking the action.   The 409 conflict is technically describing a conflict between the status of express versus implied status on the contact. The action being used to change is being done by the account owner when the email address has express permission and only actions can be taken by the contact themselves.   This is generally done with sign-up forms when a contact has been unsubscribed in addition to being deleted. ... View more

Hi @MatthewB2133,   This post is specifically referring to someone using our API to create their own sign-up form. If you are looking for a sign-up form that you do not need to write the code for yourself you can check out the link at the top of your Constant Contact account.   If you need assistance with using those sign-up forms I would highly recommend to call our support department at 866-289-2101. ... View more

Hi @InteractiveK,   Thank you for reaching out to Constant Contact's API Support.   We are currently researching this issue and working toward a solution. What is happening is what you alluded to; the email address is a deleted contact. You can do a GET on the status of DELETED and not the specific email address. This will return all deleted contacts and you should see the email address in question among those results.   That would be the work around I would recommend for now until we have a full resolution in place. If you would like to be notified of the resolution by email feel free to contact us at webservices@constantcontact.com to request this. ... View more

Hi @ErikaN02,   Thank you for reaching out to Constant Contact's API Support.   At this time Constant Contact is not making any updates to the Event product and this includes adding support to embed the registration page directly in to a website. We will be continuing to fix critical issues should they arise. If this chances I will be happy to notify you. ... View more

Hi @user88222,   Thank you for reaching out to Constant Contact's API Support.   I have sent you a separate email; please look for it at the email address attached to your Constant Contact account. ... View more

Hi @user845116,   I apologize about that. I did not notice the spelling errors. I will get this to our documentation person and have it corrected. I'll let you know when it is so you can then update your code again to the corrected versions. ... View more

Hi @user845116,   Are you able to make this call using the API Reference page? ... View more

Hi @user845116,   I've done various testing and the only way I can replicate this exact error message is when submitting to the incorrect URL i.e.  https://api.cc.email/v3/activities/add_list_membership instead of https://api.cc.email/v3/activities/add_list_memberships.   If I submit the call with an invalid listID I receive an error calling out the invalid listID. If I submit with a non-existing contactID I receive a 201 due to the bulk request being successfully made, but there is no activity actually taking place.   I know your post shows the correct URL, but can you please verify there is no leading or ending spaces or anything along those lines? ... View more

Hello @user845116,   Thank you for reaching out to Constant Contact's API Support.   I would suggest to take a look at our API Reference page to see a full example of what could be in the body for creating a contact.   You do need to include "create_source": "Account" or "create_source": "Contact" depending on whether you want the contact to reflect if it was created by the account owner or created by the contact. The last option is generally used for sign-up forms.   You also need your email address to be in the form of an array. I'm not sure exactly how you had it coded, but here is what it should look like in JSON. { "email_address": { "address": "gum2@testing.com" } Here is the full JSON for what I added to my own test account. { "email_address": { "address": "gum2@testing.com" }, "create_source": "Contact", "list_memberships": [ "17d13e10-9550-11e6-84df-d4ae5275b546" ] } Your listID will of course be different. ... View more

Hi @_Mystic_Chorale,   The potential combinations are actually covered by all the scenarios you mentioned. The OPTOUT is technically not one of those scenarios, but it does react the same way as the account owner cannot resubscribe a contact; only the contact can do that. This is the actual purpose of ACTION_BY_VISITOR.   The confirm_status in the email_addresses array can be CONFIRMED, UNCONFIRMED, or NO_CONFIRMATION_REQUIRED as listed on this page (scroll down to the Structure and click on the + next to email_addresses).   There is also a confirmed property which can be true or false. This is used to identify if the contact has confirmed their data.   Think of confirmed:true/false as a profile level confirmation and the confirm_status under the email_addresses array as an email address level confirmation. We no longer allow a contact to have more than one email address, but this is a hold over from when we did. Basically if you try to do a PUT and receive a 409 error then try again with the ACTION_BY_VISITOR parameter. ... View more

Hi @KristenZ69,   Thank you for reaching out to Constant Contact's API Support.  The ability to send an "phantom" email is not something that is available in Constant Contact. Any method of tracking when someone goes to your store with Constant Contact would generate an email or something that would notify your customer.  This is a bit outside of our realm of expertise, but I would think using Google Analytics would be your best option. When the customer scans the QR code then it would direct them to a website (visible in an app or I think this could be behind the scenes) and identify the user based on a cookie or something else on the phone.  ... View more

Hi @_Mystic_Chorale,   When you do a GET on the contact you will have the email_addresses array and that should include the opt_in_source. Here is an example:   "email_addresses": [{ "id": "d20b6d70-9029-11e3-987e-d4ae5292c47d", "status": "ACTIVE", "confirm_status": "CONFIRMED", "opt_in_source": "ACTION_BY_VISITOR", "opt_in_date": "2018-01-04T21:41:26.000Z", "email_address": "johnsmith@constantcontact.com" }], In this example the contact is express permission which you can tell in two different ways. The confirm_status is set to CONFIRMED which means the contact confirmed the information. Also the opt_in_source is ACTION_BY_VISITOR indicates this person was added in a method that reflects the contact themselves took the action. ... View more

Hi @MadiganN   Thank you for reaching out to Constant Contact's API Support.     When a contact is listed as express permission inside of the Constant Contact account then it can only be updated by that contact themselves. Express permission basically says the contact has verified the information is correct and that any changes to the information made by someone other than the contact would make the information no longer correct.   When submitting information through the API the way you tell the system that it is the contact who is making the change to the information is by using the query parameter ACTION_BY_VISITOR. Please keep in mind even a small change such as altering the first name from Robert to Bob can technically be against some of the data laws such as CASL and/or GDPR; unless the action was truly initiated by the contact directly or by permission of the contact. ... View more

Hi @_Mystic_Chorale,   Thank you for reaching out to Constant Contact's API Support.   The reason for that error is most likely due to attempting to update a contact that you do not have the permission to update. If a contact is in the implied permission status then it can be updated by the account owner or the contact. If a contact is in the express permission status then it can only be updated by the contact.   The way this is decided when using the API is by the query parameter ACTION_BY_OWNER or ACTION_BY_VISITOR. You can read about this information in our Contacts documentation: https://developer.constantcontact.com/docs/contacts-api/contacts-index.html   ... View more

Hello Everyone,   Sorry for the delayed response. As I'm sure you are already aware this issue has been resolved. We had a temporary issue with some certificates and they have been updated. Please let us know if you still see this problem. ... View more

Hello Everyone,   Sorry for the delayed response. As I'm sure you are already aware this issue has been resolved. We had a temporary issue with some certificates and they have been updated. Please let us know if you still see this problem. ... View more

Hi @SamanthaL66,   Looks like you also emailed us this request and I've replied there, but I'll give a brief answer here for anyone else who may come across this.   The base answer for this request is yes. The problem was that the Access Token was not being submitted in the HTML header. It needs to be submitted in the header as a Bearer token. If that is done then you can just submit the API calls as an HTTP request similar to how our API Tester page works. https://constantcontact.mashery.com/io-docs ... View more

Hi @StorytellerCZ,   Thank you for the detailed explanation and use case for Basic Authentication in our v3 API. I will bring this to our PO's attention. ... View more

Hi @SnaigaS,   This option is not available in our v2 API. We are looking to release these types of triggers in our website and v3 API; however we do not have any release date information at this time. ... View more

Hi @StorytellerCZ,   Your take on how the oAuth worked in v2 API is correct. We did not intend people to use our API Tester page to generate an Access Token and skip writing an oAuth flow, but that is what happened.   In a perfect development world (we all know the world is not perfect) every integration will have its own oAuth flow built in. There are a few reasons to do this, but one of the most important reasons is security. Security for both the developer and the end-user.   It seems there might be some confusion on which form of oAuth to set up as well: client-side or server-side. We will look in to making our documentation better on what each one is used for going forward. About 95% to 98% of the time an integration is going to be using server-side oAuth.   In the scenario of your newsletter subscriptions I'm not positive if this is something that is installed on your computer, or on the user's computer. If it is installed on your computer then it will only ever need one Access Token and that is for your Constant Contact account. In this case I can see how oAuth may not be as useful.   Let's take the scenario of a developer making a program for hundreds or thousands of users. I will use our WordPress Plugin as an example. It is designed to be installed on the end-users computer and require that user to authenticate with their own Constant Contact account over a website. This requires server-side oAuth because the application while installed on the end-user's computer actually runs on a web server. The end-user authenticates and then the program is able to communicate between the Constant Contact account and program.   If you hard coded the Access Token such as what happened with a lot of developers using v2 then the program would only be able to talk to the single account with which the Access Token is attached.   In actuality v2 and v3 oAuth are the same with one difference and that is Access Tokens expire faster and need to be refreshed. The ability to get around oAuth was never intended and we hope developers will use this opportunity to add a bit more security in to their programs. ... View more

Hi Scott,   We've reached out to you through an email. ... View more