Hello @SandeepN96,   Thank you for reaching out to Constant Contact's API Support.   You did not mention what error you are getting, but the most likely reason you are having problems is you are using the wrong endpoint. In order to move an existing contact in to a different list you will need to update the contact using a PUT. https://developer.constantcontact.com/docs/contacts-api/contacts-resource.html?method=PUT ... View more

Hi @DonnaH072,   The reason our oAuth was designed this way is for security reasons. If an Access Token is compromised it will expire in a relatively short amount of time so the potential "damage" that can be caused is minimal.   You are very close to using the oAuth flow how we intended it to work. You are manually getting a new Access Token every two hours. We actually intended for the Allow button to be clicked once, generate the first set of Access/Refresh Tokens, then store those tokens to be used.   When the Access Token expires (between two hours and twenty-four hours later) then you use the Refresh Token to generate a new Access/Refresh Token set, delete the old set and save this new set. This is the Step 5 in the server oAuth flow. ... View more

Hi @SilviaG20,   The authorization code from Step 3 expires after 60 seconds; are going able to move from Step 3 to Step 4 quickly enough for the code to not expire? ... View more

Hello @SilviaG20,   Thank you for reaching out to Constant Contact's API Support.   In the My Applications page you can click on the API Key. On that page there is a button to click on to generate your Client Secret. The secret is only shown once so you will need to save this somewhere. If you click on the button again it will generate a new secret and negate the previous secret. ... View more

Hello @user431876,   Thank you for reaching out to Constant Contact's API Support.   The reason for this email is due to sending an email campaign to a contact list that did not have any contacts in it. You will need to ensure that the contact list has contacts and that you do not delete those contacts until after the email campaign has been sent.   If you are resending the email campaign you need to make sure the contact list has new contacts that have not previously received the campaign. ... View more

Hello @user431876,   Thank you for reaching out to Constant Contact's API Support.   It is a Federal requirement to display the footer information and part of that information requires a physical address. This is part of the Federal CAN-SPAM ACT. ... View more

Hi @_Mystic_Chorale,   The v3 API sends/receives data exactly the same as our v2 API; it is a RESTful API. The data payload is formatted in the JSON format and the endpoints are just http requests. How you choose to write that in your code is completely up to you. Our v2 SDK did use a cURL library to accomplish it's requests.   In regards to how your integration currently works with adding contacts and adding them to the contact lists. The v3 works in the same way. The ID format for contacts and lists has changed format, but that will not change how your integration works.   General Questions 1. There are no new status or anything. The creation process is the same; there is added functionality if you want to use it such as birthdays and anniversaries.   2. The contact list is now considered to be a sub resource which is why it is a separate array. Each sub resource is its own array within the main object. Here is an example of how I would format the JSON.     { "email_address": { "address": "xxxx@example.com", "permission_to_send": "implicit" }, "first_name": "xxxx", "last_name": "xxxx", "create_source": "Account", "list_memberships": [ "xxxxx" ] }     3. Our documentation should show an example for a single contact creation as well as a bulk import from csv. Here is the link to the single contact creation. https://v3.developer.constantcontact.com/api_guide/contacts_create.html#example-post-create-a-contact-request ... View more

Hello @_Mystic_Chorale,   Thank you for reaching out to Constant Contact's API Support.   Our primary focus is developing our v3 API which means we are not updating on our SDKs for v2. I am happy to answer any questions you have regarding replicating your integration in the v3 if that is your best option. Feel free to post your questions here, or if the information needs to remain private you can reach us by emailing webservices(at)constantcontact(dot)com. ... View more

Hi @HonestA,   Would you mind sending an email to webservices(at)constantcontact(dot)com with the data you are importing along with your API Key so we can check our logs and dig in to this more? ... View more

Hi @user431876 and @HonestA,   The 5xx errors should be resolved now. ... View more

Hello @user431876,   Thank you for reaching out to Constant Contact's API Support.   Have you tried to send a test using our UI? The most common reason for not receiving a test send is due to deliverability issues. Generally this means that the test send was actually received (due to the success 204), but it went in to a spam folder. ... View more

Hi @HonestA,   The cf fields will only work if they have already been created using the Custom Fields endpoints. Consider the cf fields to be an alias that is pointing to the custom fields, so they need to be created before the alias will work.   If you have already created the custom fields using the necessary endpoints let us know and we can look in to this further. ... View more

Hello @dfgdrr,   Thank you for reaching out to Constant Contact's API Support.   You also emailed us and due to the nature of the information needed to troubleshoot please look for our email reply and we will work through that method. ... View more

Hello @IntegrationT4,   Thank you for reaching out to Constant Contact's API Support.   We are currently experiencing a system issue that is causing these 5xx errors. Our engineers are hard at work looking for a resolution. Once we have a fix in place we will have more information to share. ... View more

Hello @SilviaG20,   Thank you for reaching out to Constant Contact's API Support.   We are currently experiencing a server issue that is causing the frequent timeouts. We are working diligently to find the cause and implement a fix for this. For security reasons our API does not support javascript. For your listID you can use the below endpoint; of course we are experiencing the timeouts which will cause problems right now. https://v3.developer.constantcontact.com/api_reference/index.html #!/Contact_Lists/getLists ... View more

Hello @ericg5327,   Thank you for reaching out to Constant Contact's API Support.   You mention that you are stuck on generating the Access Token. When using our v3 API you do need to go through the oAuth flow, either client or server, to generate an Access Token. Even if you are the user this process is still required. The Access Token is what identifies which Constant Contact account you want to send data to and receive data from.   Once you have established that portion of your program you can then create your email. You can see a code sample of a POST on this page. ... View more

Hi @user96514,   Sorry your message fell off. We'll take a look and get back to you. ... View more

Hello @xingmingm2,   Thank you for reaching out to Constant Contact's API Support.   That error indicates that you have not included a valid and verified email address in the reply-to field for the email address. If you have not already verified an email address for your account you need to do that first. Once you have verified an email address you can set that address as the reply-to address. ... View more

Hello @user431876,   Thank you for reaching out to Constant Contact's API Support.   There are a few different things that can cause that error. If this is a new account make sure that your account has the physical address set under the My Settings section. Also make sure that you have verified the reply-to and from address you are using.   As for email campaign specific issues make sure that you have assigned a contact list to the email and ensure that you have set a valid send time. If all of these are set and correct can you please provide a code snippet of what you are submitting when this error occurs? ... View more

Hello @ThomasB865,   Thank you for reaching out to Constant Contact's API Support.   Are you attempting to use the server flow or the client flow? ... View more

Hello @ShelleyM2 ,   Thank you for reaching out to Constant Contact's API Support.   Looks to be a syntax error. You have both a ? and & before api_key. Since this is the first (and only) query parameter you just need the ?. ... View more

Hello @user151814,   Thank you for reaching out to Constant Contact's API Support.   Using cf: is basically a shortcut/alias for custom fields. It only works if the custom field has already been created so that the cf: command has a name it can reference. You can create the custom fields separately from creating the contact by using the custom field endpoints. Once you have all of your custom fields created then you should be able to reference them using the cf: during a bulk import.   https://v3.developer.constantcontact.com/api_guide/custom_fields.html ... View more

Hello @PaulH035,   Thank you for reaching out to Constant Contact's API Support.   Our API can provide the reporting data; however the data would be provided in a JSON response and not in a csv file. You would need to take the data and add it to a csv file on your end. Currently all of the reporting endpoints are available with our v2 API and our v3 API will have the reporting endpoints released over a few releases still. ... View more

Hello @AdamM5071,   Thank you for reaching out to Constant Contact's API Support.   We appreciate you bringing this to our attention. We'll go over the possibilities and update the file as needed and get back to you. ... View more

Hi @GoldenRetrieverR,   That error message occurs when the Refresh Token you used was invalidated by generating another Refresh Token. When using the oAuth flow you would generate one Access/Refresh Token for a single Constant Contact account and then use that Refresh Token to generate a new Access/Refresh Token. When you generate the new Access/Refresh Token this will invalidate the previous tokens. ... View more

Hi @JonA63399,   You can do a GET to see a deleted contact. You must include the email address and you must include a status of either all, or deleted. This will return a result of the contact that looks like this.   "contacts": [ { "contact_id": "d4e514d4-9d0b-11e9-9bfe-d4ae528e486a", "email_address": { "address": "msm005@ucsd.edu", "permission_to_send": "implicit", "created_at": "2019-07-02T16:56:17-04:00", "updated_at": "2019-09-09T11:56:37-04:00", "opt_in_source": "Account", "opt_in_date": "2019-07-02T16:56:16-04:00", "confirm_status": "off" }, "first_name": "Micaela", "last_name": "Martinez", "create_source": "Account", "created_at": "2019-07-02T16:56:17-04:00", "updated_at": "2019-09-09T11:56:37-04:00", "deleted_at": "2019-09-09" }, ... View more

Hi @CarolynG105,   Our API cannot currently interact with Welcome Emails or Automated Emails. You can create one of those by logging in to your account, create it, and schedule it. You can then use the API to add contacts to the list that email is scheduled to send to; since it is a Welcome/Automated email it will automatically send out to anyone that joins the list.   You cannot use the API to create or edit that email. ... View more