Hi @MerrellM and @MyronS,   Constant Contact does not have a listserv style option at this time. To my knowledge we are not currently looking to develop this in house; however I'm happy to submit your request to our developers and let them know of your interest. ... View more

Hi @JohnW4437,   The initial token requires user interaction; this was also the case with our v2 API. There was no way you could get an Access Token with our v2 API that did not involve the owner of the Constant Contact account interacting and granting permission to your application.   When using the v3 API this initial token will also require user interaction, but that is the only time that it will be required. After you have the initial token you can store that data just like when using the v2 API. However; after two hours have passed you will be prompted that the token has expired. In that instance you will then need to go through the refresh portion of the v3 oAuth. The refresh portion does not require interaction from the user.   When doing the refresh part of oAuth you will be provided with a new Access Token which you will replace the original token with and it will last for two hours. After which you will need to go through the refresh portion again. Please keep in mind the refresh portion can all be coded to happen automatically so that it does not require any interaction from the developer or the user.   You can see both a cURL and PHP example of the full oAuth process here. ... View more

Hi @JohnW4437,   The Access Token with our v2 API technically expires and it can be set to expire quicker, but the default is  315359999 seconds which is about 10 years. You can view this in our documentation here. Search for "Access Token Response" and it is in that section.   When we released our v3 we decided that wasn't the most secure of expiration timeouts so we changed it to expire quicker. However; once you get the Access Token while you will not want to hard code that anymore you can still write your code to refresh that automatically without any further user interaction. ... View more

Hi @JohnW4437,   Our v2 API required user interaction for authentication as well. The difference is the v2 API did not expire for a long time where as the v3 API expires in about 2 hours. However; once you do the initial user interaction (which was required in v2) then any additional refresh can happen automatically if you write your oAuth code correctly.   The part of oAuth in both v2 and v3 API that needs to have user interaction is when the user logs in to their Constant Contact account and clicks allow. After this everything else can be automated. ... View more

Hi @ErikT825,   Our v3 API has limited release. The contacts endpoints are available, but as you noticed there is currently not a way to add tags. Our engineering teams are comparing the use of tags versus segmentations in the UI and will implement which ever one does better in the v3 API. ... View more

I'm not sure exactly which language you are using; however if you were to make this a generic http request like the original message says this is what it would look like.   https://visitor2.constantcontact.com/api/signup?ca=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx&email=email@sample.com&first_name=Joe&list_1=xxxxxxxxxx&list_2=xxxxxxxxxx ... View more

Hi @TomB02198,   Please keep in mind as the subject of this post lists that this method is deprecated so support is very limited.   Your lists need to be in an array with each one having a different name. Here is an example: 1. { 2. "contact_lists":["list_id1","list_id2"], 3. "list_name":"list_name", 4. "source":"My App" 5. } contact_lists : array : Array of Contact List Ids that the new contact will be added to. REQUIRED if list_name is not specified. list_name : string (255) : Specifies the name of the list that the new contact will be added to. The Contact list is created if it does not exist. REQUIRED if contact_lists are not specified. ... View more

Hi @HowardG197,   Thank you for reaching out to Constant Contact's API Support.   If you use an email template from our website UI you will not be able to use the API to edit or add content to that email template. In order to use the API to edit an email you will want to use what we call an custom code email. That is an email that uses your own HTML. You can read our documentation for this here. ... View more

Hi @Headz_Up,   I was able to just register a new application and get a new API Key. What error message are you getting when you visit that page? Can you provide a screenshot? ... View more

Hi @BoKruck,   The invalid redirect message generally only occurs if the redirect URI is different in the integration compared to the value listed in your Mashery account. If you are the developer of the integration then this is something that you can change on your own. If you did not develop the integration then you would need to reach out to the developer so they can make sure those values match.   I cannot speak to the requirement of having to upgrade to a different version of Goldmine in order to continue using it as Constant Contact did not create the integration. You may want to check on our Marketplace to see if there are any other alternate options for you. ... View more

Hi @clarisam4,   Your integration needs to connect to a Constant Contact account in order to know where to add the email address. The way that your integration connects to the account is through oAuth; the end result of oAuth is to get an Access Token.   The API Key allows your integration to talk to our system. The Access Token tells our system which Constant Contact account to send/retrieve data from.   It sounds like you are making a type of sign-up form. In that situation all of the authentication would happen behind the scenes. The "client/people" that are signing up do not have to authenticate. Your integration aka script is what needs to authenticate. In the v2 API you did this by using the API Key and Access Token which you also may know as a Bearer number.   It may be beneficial at this point to have you email us at webservices@constantcontact.com so you can provide us your specific information and we can give more detailed specifics that should not be shared publicly. ... View more

Hi @clarisam4,   You would want to use server flow. The client flow would be used in a scenario where your application runs solely on the clients end.   In your scenario you are running everything on your end and storing data there as well. The only thing the client will be redirected for is they will be prompted once to enter their Constant Contact username and password. Once they do this and Allow your application to connect to their account then your application will get an Access Token to connect to their account. After that the oAuth flow has steps for you to refresh that token as needed. ... View more

Hi @clarisam4,   Using the Try It button does authenticate and create an Access Token which is the Bearer ID that you located by checking the Network tab. Please keep in mind that will expire and you will need to get a new one.   That is why we suggest that you write your own oAuth code and we have provided both cURL and PHP examples if you check on oAuth sections of the API Docs. You can scroll through that link and there will be example sections with tabs to show you both of the coding examples to write your own oAuth flow. ... View more

Hi @clarisam4,   The v3 API uses the same authentication method as our v2 API did with one exception. The Access Tokens expire more frequently now so there is a method to refresh them. Here is the location for our oAuth documentation.   https://v3.developer.constantcontact.com/api_guide/auth_overview.html ... View more

Hi @jab538,   We have not yet made an official announcement; however the contacts features of our v3 API have been released. You can access them at the below link.   https://v3.developer.constantcontact.com/index.html ... View more

Hi @clarisam4,   Thank you for reaching out to Constant Contact's API Support.   Our current v2 API was designed with our older Contacts system. Our website has been updated to a new version of the Contacts system. We have recently released our contacts features for our v3 API that includes these features.   We are still working on making an announcement which is why no one knows about it yet, but since this is what you are looking for I've provided the link below.   https://v3.developer.constantcontact.com/index.html ... View more

Hi @SebastianM52,   Thank you for reaching out to Constant Contact's API Support.   The current version of our API is using and older version of the contacts system compared to what is available in our website UI. This means that the API does not currently support custom names when using the custom fields. You will need to use the naming structure of CustomFieldn . You can reference the below link for the differences between the API and the website.   http://developer.constantcontact.com/docs/contacts-api/api-gui-func.html ... View more

Hi @ColinM421,   Thank you for this information. I'll pass this along to our engineers and see what they can do with this. ... View more

Hi @ToddV8,   The embedded code form that the above posts are referring to is no longer available to new accounts. If an older account still have the form active on a website the code will work and the code can be edited.   We have decided to move away from that older HTML form towards a more streamlined form that is not available within the Constant Contact account under the link for Sign-Up forms.   Because we have moved away from the older style of HTML form the articles referring to it have also been removed. I will make sure to edit the above post to remove the link since it no longer works. ... View more

Hi @TradersVillage,   Thank you for reaching out to Constant Contact's API Support.   I would do it basically how you mention. Assuming your database is the one with the most recent and correct data then I would first clear out the lists of contacts in your Constant Contact account. Then submit your new/updated list of contacts to the correct list within Constant Contact. If you want to use bulk methods here is how I would order them.   1. http://developer.constantcontact.com/docs/bulk_activities_api/bulk-activities-clear-contactlists.html?method=POST (this can be used to clear both lists with one API call)   2. http://developer.constantcontact.com/docs/bulk_activities_api/bulk-activities-addcontact-multipart.html?method=POST (this is used to POST contacts using a csv file to the list)   3. http://developer.constantcontact.com/docs/bulk_activities_api/bulk-activities-addcontact-multipart.html?method=POST (same as step 2, just do this for which ever list you did not pick in that step)   Using those import bulk methods sets the parameter to ACTION_BY_OWNER which means you will not be able to add contacts that have unsubscribed. ... View more

Hi @user7498,   Thank you for reaching out to Constant Contact's API Support.   That document gives you steps on how to install our PHP SDK. It does not have any information on writing your own HTML.   Are you having problems installing the library itself? If so what error messages are you receiving during the install process? ... View more

Hi @DanP25,   Thank you for reaching out to Constant Contact's API Support.   Retrieving an email from the API, or viewing the email in the website, will give you the same information. The data from a custom field is only filled out when the email is sent live. You will not see that data in the email unless you are the recipient of the email. If you need to know the information that should be in the those custom fields you would want to look at the individual contact and review the data associated with the custom field directly. ... View more