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.
Once you find a developer to assist with your project, the below info may be of use when updating from V2 to V3:
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, rather than just accessing the account via your username and password.
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:
While the rest of our documentation is linked from the quick start guide, the following pages in particular may be useful:
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:
While Constant Contact doesn’t offer any services as far as assistance with building custom integrations, and 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 or your developer have any other questions!
You can also reach our team directly at email@example.com