Hello user643957,   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.   Our V3 API does use API keys. Step 2 of the documentation I am linking below contains instructions on how to generate them.   V3 API Quick Start Guide: https://developer.constantcontact.com/api_guide/getting_started.html   Once you have generated a V3 API key, our available OAuth2 flows are used to authorize it on an account and generate an Access Token, which can be used to make authorized calls to the standard V3 endpoints. Each of our authorization flows requires the use of a browser window for a user to grant access to an application for their Constant Contact account through a permission request screen, however, you should only need to do this once as after access has been granted, your application can maintain account access through the use of refresh tokens.   If you don’t want to use redirects for authorization, I would recommend looking into our device flow, which doesn’t use redirects or the client secret. I’m including documentation for this authorization flow below.   OAuth2 Device Flow: https://developer.constantcontact.com/api_guide/device_flow.html   I see that a V3 API key has been generated under your account, however, I’m not seeing any authorization requests made using it in our logs. The error you encountered would typically indicate that an invalid client ID/API key was used in the request. We would be happy to investigate this further if you can reach out to webservices@constantcontact.com with a full example of your authorization request, including headers.   Please let us know if you have any other questions!   Regards, ... View more

Hello SeanO0313,   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.   You are correct that the universal code currently connects all form types to your Constant Contact account and it is not possible to separate pop-up/flyout forms from inline forms on pages where the universal code is installed. We greatly appreciate your feedback about this functionality. We do have an open feature request for unique universal codes for pop-up, flyout and banner forms to allow for further customization of which forms appear on which pages of websites. I have tracked your account on this feature request, although I am not able to guarantee if or when this feature will be implemented.     Please let us know if you have any other questions!   Regards, ... View more

Hello user76761,   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.   It looks like we've already followed up with you directly via email, but here is the information provided for visibility on the forum:   The Bulk Activity endpoints do have some limitations as far as request and file size, so there are a couple of different options available.   While you could try just pulling by list (pending that no single list exceeds that amount), you may have an easier time just using GET /contacts and using the pagination functionality, which is not available for bulk endpoints.   GET Contacts Collection https://v3.developer.constantcontact.com/api_reference/index.html#!/Contacts/getContacts   When using GET /contacts, you'd want to include whichever contact details are desired, and then set the "limit" query parameter to '500' which is the maximum amount of results that can be returned per call from this endpoint. When you get the response body with those 500 contacts, there will also be a line entry at the end of the results labeled like this:   "_links": {     "next": {       "href": "/v3/activities/{activity_id}"     }   },   You would then make a follow-up call to GET /v3/activities/{activity_id}"  using the URL returned for the next page of results (each page will return a different URL), and keep doing this until there is no "next" result at the end of the response body, which will indicate you have reached the end of all of the contacts.   Please have a look and let us know if you have any other questions!   Regards, ... View more

Hello HopeStarter, user402918, TeresaD68348 & user74392,   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.   The 3rd party Divi/Bloom plugin uses our legacy V2 API. V2 API keys and Access Tokens can no longer be created as the platform used to generate them (constantcontact.mashery.com) has been retired in preparation for the full retirement of the V2 API. I’m sorry for any inconvenience this may cause. I would highly recommend reaching out to the Divi/Bloom team to see if they have plans to move the integration over to our current V3 API, or if a V3 integration is available but not yet publicly listed. Below I’m including a link to their support team.   Divi/Bloom Support: https://www.elegantthemes.com/contact/   Please have a look and let us know if you have any other questions!   Regards, ... View more

Hello user99160,   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 currently have an open ticket for this issue with our engineering teams. We do not yet have an ETA on when this issue will be resolved, however, I have set up your account to receive an email notification as soon as a resolution has been reached.    If you have further questions regarding this issue, please reach out to Constant Contact's Support Team at 866-289-2101 and reference case #33266676.   Regards, ... View more

Hello ColinHuronCoC,   Thank you for your reply.   We still have an open ticket for this error occurring specifically when sending email campaigns through the Constant Contact website. We do not yet have an ETA on when this issue will be resolved, however, I have set up your account to receive an email notification as soon as a resolution has been reached.    If you have further questions regarding this issue, please reach out to Constant Contact's Support Team at 866-289-2101 and reference case #33266671.   Regards, ... View more

Hello ChadO60,   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.   I apologize for the delay in our response. It appears that this error was occurring due to an account status that has since been lifted. You should now be able to successfully create new API keys. If you are still experiencing this error, please reach out to us via email at weebservices@constantcontact.com.   Please let us know if you have any other questions!   Regards, ... View more

Hello Anis_LLL,   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.   I apologize for the delay in our response. It appears that this error was occurring due to an account status that has since been lifted. You should now be able to successfully create new API keys. If you are still experiencing this error, please reach out to us via email at webservices@constantcontact.com.   Please let us know if you have any other questions!   Regards, ... View more

Hello user3132378,   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.   Thank you for providing the screenshot of the error report. It looks like we'll need some additional information in order to assist with troubleshooting. If you could please provide us with your API key, a full example authorization request, including headers, and any timestamps or general timeframes you may have for when this error has occurred, we'll be able to better assist in pinpointing the cause of the error. Please provide this information securely by reaching out to us via email at webservices@constantcontact.com, we look forward to assisting you!   Please let us know if you have any other questions!   Regards, ... View more

Hello VictorianFarmsteadP,   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.   I’m sorry to hear that you’ve been encountering this error. It looks like we'll need some additional information in order to assist with troubleshooting. If you could please provide us with your API key, the specific requests that have resulted in this error, and any timestamps or general timeframes you have for when this error has occured, we'll be able to better assist in pinpointing the cause of the error. Please provide this information securely by reaching out to us via email at webservices@constantcontact.com, we look forward to assisting you!   Please have a look and let us know if you have any other questions!   Regards, ... View more

Hello ClaudiaC14,   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.   It looks like we've already followed up with you directly via email, but here is the information provided for visibility on the forum:   I’ve reviewed your request and found that the reason for the 404 response is that there is a typo in the request URL.    In your request, the URL is formatted as follows: “https://api.cc.email/v3/contact_lists/lists_id_xrefs”   Our system is expecting this URL to be formatted as follows: “https://api.cc.email/v3/contact_lists/list_id_xrefs”   There is an additional “s” in the “list_id_xrefs” portion of the URL. Removing this extra character should allow your request to be successful. Please have a look and let us know if you have any other questions!   Regards, ... View more

Hello user897433,   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.   It looks like we've already followed up with you directly via email, but I wanted to close the loop here as well. If you haven't received our reply, please let us know via email at webservices@constantcontact.com, and reference case number 33254065.   Please have a look and let us know if you have any other questions!   Regards, ... View more

Hello CarlosL6961,   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.   It looks like we reached out to you via email regarding this issue to request some additional information in order to better assist with troubleshooting. If you still need assistance with this, please let us know! If you haven't received our reply, please let us know via email at webservices@constantcontact.com, and reference case number 33248536.   Please have a look and let us know if you have any other questions!   Regards, ... View more

Hello BrianB7795,   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.   Each of our available authorization flows requires the use of a browser window for a Constant Contact user to authorize an application/integration on their account, however, you should only need to do this once as after authorization has been granted, your application/integration can utilize Refresh Tokens to maintain account access.   Please let us know if you have any other questions!   Regards, ... View more

Hello user9377357,   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.   It looks like we'll need some additional information in order to assist with troubleshooting. If you could please provide us with the V3 API key that you’re using, a full example authorization request, and any timestamps/general timeframes you may have for when you encountered this issue we'll be able to better assist in pinpointing the cause of this error. Please provide this information securely by reaching out to us via email at webservices@constantcontact.com, we look forward to assisting you!   Regards, ... View more

Hello kevincarbon,   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.   There isn’t a way to edit the inline and pop-up sign-up forms beyond the customization that is available in the website UI, however, you could utilize our V3 API to build your own custom sign-up form. Below I’m including documentation for our sign_up_form endpoint, which has similar functionality to that of the inline and pop-up forms offered in the website UI.   Create or Update a Contact: https://developer.constantcontact.com/api_reference/index.html#!/Contacts/createOrUpdateContact   While our expertise is with our API itself as opposed to its implementation within any particular programming language, we are happy to answer any questions pertaining to Constant Contact’s API endpoints, functionality, and documentation.   Please have a look and let us know if you have any other questions!   Regards, ... View more

Hello DavidH0222,   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.   Constant Contact provides developers with free access to our V3 API endpoints for developers building their own application for integration. You can get started using our API by visiting our documentation here: https://v3.developer.constantcontact.com/api_guide/getting_started.html    Our developer portal uses the same credentials and login session as your Constant Contact account. As a side note though, V3 API keys generated via the Developer Portal are not universal to the account and can only be accessed by the logged in user that created them.   Additionally, you can utilize our API Reference Page to find body schemas & values, as well as test the functionality of our available endpoints to see how they will work once programmed within your application: https://v3.developer.constantcontact.com/api_reference/index.html   While our expertise is with our API itself as opposed to its implementation within any particular programming language, we are happy to answer any questions pertaining to Constant Contact's API endpoints, functionality, and documentation. Please have a look and let us know if you have any other questions!   Regards, ... View more

Hello BrendanS6,   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.   Constant Contact provides developers with free access to our V3 API endpoints for developers building their own application for integration. You can get started using our API by visiting our documentation here: https://v3.developer.constantcontact.com/api_guide/getting_started.html    Our developer portal uses the same credentials and login session as your Constant Contact account. As a side note though, V3 API keys generated via the Developer Portal are not universal to the account and can only be accessed by the logged in user that created them.   Additionally, you can utilize our API Reference Page to find body schemas & values, as well as test the functionality of our available endpoints to see how they will work once programmed within your application: https://v3.developer.constantcontact.com/api_reference/index.html   While our expertise is with our API itself as opposed to its implementation within any particular programming language, we are happy to answer any questions pertaining to Constant Contact's API endpoints, functionality, and documentation. Please have a look and let us know if you have any other questions!   Regards, ... View more

Hello SyncApps-Expert,   Thank you for your reply.   We do yet have a date set for V2 deprecation, however, it may potentially happen as soon as this year. Any future deprecation-related notices for V2 communications will likely be sent specifically to whichever email address was registered in the Mashery Developer portal  (https://constantcontact.mashery.com/) for the legacy V2 API key that the integration uses to connect.    Please let us know if you have any other questions!   Regards, ... View more

Hello DavidM0436,   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.   It sounds like you may be trying to use a 3rd-party app that is asking you for an API Key. Usually an application developer will generate their own API Key that lets their app integrate with Constant Contact, however some developers require you to provide them with an API Key. Since this process was designed to be done by the app developers themselves, it can be confusing for end users to find or generate this information.   We have two different versions of our API, which are managed through different platforms and are not cross compatible.   If the app you are using is asking you for an API Key and Secret, then it most likely utilizes our current V3 API.  Your 3rd party integration may also provide you with the Redirect URI to add to your key's settings.    For a V3 API key, please follow steps 1-3 at the following link.: https://v3.developer.constantcontact.com/api_guide/apps_create.html   Otherwise, if the app you are using is asking you to also provide an "Access Token" with your API key, then it most likely utilizes our legacy V2 API, for which keys can no longer be created.   For over 3 years, we have considered creation of new V2 API Keys to be unsupported, as noted within our V2 API documentation. The Constant Contact Mashery Portal at 'constantcontact.mashery.com' has now been retired & creation of V2 API Keys is no longer possible. For any new development, please utilize our V3 API.   https://community.constantcontact.com/t5/API-Developer-Support/Creation-of-V2-API-Keys-Has-Been-Retired/td-p/427083   If you are a customer looking to use a 3rd party developed integration/form/plugin that is asking you for an API key and access token, or is asking you to generate an API key/token/secret via constantcontact.mashery.com, you will not be able to connect with this integration. Additionally, V3 keys generated within the Constant Contact Developer Portal (v3.developer.constantcontact.com) are NOT cross compatible with integrations that were built using V2, and will not work to connect with these legacy integrations.   If this is the case, please feel free to email us with the name of the  3rd party developed integration/form/plugin that you were trying to connect with, as well as links to their website/documentation, and we'd be happy to take a look and see what other comparable options may be available to look into.   If you are not the developer of the integration and have any concerns about this, please contact the integration/form/plugin's developer directly to see what their plans are, regarding updating their integration to V3. If the developer has any questions or concerns, you're welcome to have them follow up with us directly via email at webservices@constantcontact.com with any questions.  (*If you are not sure who the developer is or how to contact them, please let us know the name of the 3rd party plugin/integration/form that you are using and any additional relevant information so that we can try to provide further direction.)   If you are a developer looking to access/manage your existing keys within the Mashery Portal, you will no longer have access to the portal, though existing V2 API keys will continue to function. If any business critical changes are needed for existing V2 API keys, please email us with the API key value as well as the nature of your request, and we will see if it is something we may be able to modify from the back end of the account.   While no date is currently set, there will be a point in the near future where our legacy V2 API will begin deprecation, potentially as soon as some point this year, at which point integrations using V2 will stop working. Due to this, while we will continue to deploy critical bug fixes at this time, we will not be doing any more development for V2 or its endpoints.   If you are the developer of the integration, we strongly recommend updating the integration to use our V3 API as soon as possible, to ensure you're ahead of the curve. Our current V3 API uses OAuth2.0, which is the current industry-standard for authorization. It's more secure and does a much better job of keeping your Constant Contact account data safe. When you give their integration permission to access your account, it will show you exactly which permissions the integration is requesting to be granted (rather than just granting all permissions). V3 also uses tokens that are continuously refreshed to keep the connection encrypted and secure.   There are several significant differences between our V2 and V3 APIs, including the use of different endpoints, OAuth 2.0 rather than basic authentication, JSON payloads instead of XML, and a different format for resource identifiers.   A quick start guide for the V3 API can be found here: https://developer.constantcontact.com/api_guide/getting_started.html    While the rest of our documentation is linked from the quick start guide, the following pages in particular may be useful: https://developer.constantcontact.com/api_guide/v3_technical_overview.html  https://developer.constantcontact.com/api_guide/developer_portal.html  https://developer.constantcontact.com/api_guide/migration_overview.html    Additionally, you can utilize our API Reference tester to test out the functionality of our available endpoints to see how they will work once programmed within your application:  https://v3.developer.constantcontact.com/api_reference/index.html    If you would like us to send you additional information regarding getting started with V3 authorization and/or endpoints, or have any further questions, please feel free to reply directly to this email so that we can assist further.   Please have a look and let us know if you have any other questions!   Regards, ... View more

Hello IT-Admin,   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.   I’m sorry to hear that you’ve been running into this error. If you’d like to provide us with example contacts who have run into this error when being added to your account, we would be happy to investigate and confirm the reason for the error. You can reach out to us directly with this information at webservices@constantcontact.com.   I would also mention that our engineering teams are currently working to improve the overall experience with our compliance system check when adding contacts.    Please let us know if you have any other questions!   Regards, ... View more

Hello user544507,   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.   Upon doing some research on the error you encountered, I found that this can occur as a result of an update to the cURL version that your application is using, or with an HTTP configuration issue on the server your application is running on.   While our expertise is with our API itself as opposed to its implementation within any particular programming language, we are happy to answer any questions pertaining to Constant Contact’s API endpoints, functionality, and documentation.   Please have a look and let us know if you have any other questions!   Regards, ... View more

Hello AidanO03,   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.   For now, the only webhooks we offer are for Partners (and those are only related to billing/billing status). We don't yet offer webhooks for individual accounts' contacts, campaigns, etc.   Please let us know if you have any other questions!   Regards, ... View more

Hello TXHB,   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.   I have tracked your account on the open feature request for the ability to enable SSO for standard accounts.   Please let us know if you have any other questions!   Regards, ... View more

Hello JasonM15890,   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.   The request for V3 application code samples is currently under review. However, we're currently still adding endpoints and capabilities to the V3 API, and do not plan to publish official sample apps until that process is complete. Your feedback and experience with this request is essential to improving our product, so thank you for reaching out to us regarding this matter.   For updates on which new features and endpoints have been released for Constant Contact's V3 API, you can stay updated by checking the Constant Contact V3 API Release Notes page:   V3 API - Release Notes https://developer.constantcontact.com/api_guide/index.html   In the meantime, here are the example calls that are currently available for V3:   V3 Code Samples: https://v3.developer.constantcontact.com/api_guide/tag_code_samples.html    Additionally, you can utilize our API Reference tester to test out the functionality of our available endpoints to see how they will work once programmed within your application: https://v3.developer.constantcontact.com/api_reference/index.html   The Client Secret is used to authorize requests made to the authorization server. You can obtain your application’s client secret in the Developer portal with the following steps:   Login to your account at https://app.constantcontact.com/pages/dma/portal/ Select the name of your V3 API key Select the blue “Generate Client Secret” button under the “App Details” section of the “Details” tab.   Please have a look and let us know if you have any other questions!   Regards, ... View more

Hello NateP57,   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 now offer the Device authorization flow for the V3 API which is intended for applications which run on devices that are input constrained. This authorization flow does not require the use of redirect URLs, callbacks, or the client secret. I’m including our documentation on this flow below.   OAuth2 Device Flow: https://developer.constantcontact.com/api_guide/device_flow.html   Please have a look and let us know if you have any other questions!   Regards, ... View more

Hello NickB331,   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.   It looks like we've already followed up with you directly via email, but I wanted to close the loop here as well. If you haven't received our reply, please let us know via email at webservices@constantcontact.com, and reference case number 31225770.   Please have a look and let us know if you have any other questions!   Regards, ... View more