The Community is hosting an End of Summer sweepstakes! Participants must complete tasks to earn tickets that will enter them with a chance to win a free year of Constant Contact and other great prizes!*
*No Purchase Necessary. For Official Rules, visit here. Constant Contact’s End of Summer 2020 Sweepstakes ends on October, 20, 2020 at 11:50 PM EST.

API v1 - Is it staying or eventually being cut?

SOLVED
Go to solution
Highlighted
Occasional Contributor

API v1 - Is it staying or eventually being cut?

Hi,

 

The subject pretty much explains this post. I'm aware that the api was upgraded to v2 but v1 functionality is still accessible. Just wondering if you plan to keep support for API v1 or pull the plug (if so what date?). I've done a little research on v2 but haven't found an answer to this.

 

If it's not getting cut, how long will it be staying?

 

Thanks.

-Paul

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Moderator

Re: API v1 - Is it staying or eventually being cut?

Hey Paul,

 

We have deprecated V1 already and put it in "maintenance mode" only, meaning no new functionality will be developed for it and we will only be fixing defects.  We will also not be rolling out any new product features and functionality for existing endpoints through the V1 API. 

 

We also intend to put an end of life out for the V1 API once we have complete coverage for all endpoint in the V2 API.  This includes partner only API endpoints, which is the majority of the missing functionality in V2.  Once we have this complete and all the resources available for developers to migrate over to the new version, we will notify developers that we are ending the life for V1 and provide the date which that goes into effect.  We do plan on providing plenty of lead time to our developer community as well as tools and libraries to help make this as simple a transition as possible.

 

If you are doing new development, we highly recommend you do that on the V2 API.  If you find that there is something you can't do in the V2 API that you could do in the V1, let us know by emailing webservices@constantcontact.com or posting here in the forums. 

Dave Berard
Senior Product Manager, Constant Contact

View solution in original post

3 REPLIES 3
Highlighted
Moderator

Re: API v1 - Is it staying or eventually being cut?

Hey Paul,

 

We have deprecated V1 already and put it in "maintenance mode" only, meaning no new functionality will be developed for it and we will only be fixing defects.  We will also not be rolling out any new product features and functionality for existing endpoints through the V1 API. 

 

We also intend to put an end of life out for the V1 API once we have complete coverage for all endpoint in the V2 API.  This includes partner only API endpoints, which is the majority of the missing functionality in V2.  Once we have this complete and all the resources available for developers to migrate over to the new version, we will notify developers that we are ending the life for V1 and provide the date which that goes into effect.  We do plan on providing plenty of lead time to our developer community as well as tools and libraries to help make this as simple a transition as possible.

 

If you are doing new development, we highly recommend you do that on the V2 API.  If you find that there is something you can't do in the V2 API that you could do in the V1, let us know by emailing webservices@constantcontact.com or posting here in the forums. 

Dave Berard
Senior Product Manager, Constant Contact

View solution in original post

Highlighted
Developer

Re: API v1 - Is it staying or eventually being cut?

What is the end of life date for API v1 or has it already past? 

Highlighted
Moderator

Re: API v1 - Is it staying or eventually being cut?

We have not set a date yet for ending access to v1.  However, as mentioned above, we are no longer adding new functionality with our new products and services.  We are also only maintaining backwards compatibility with core functionality, I.E. some fields are depricated and no longer supported but are returned solely to maintain XML parsing.  We highly recommend using the v2 API at this point as it is both functionality on par as well as being actively maintained with new functionality, services and continues to have better data access.

Dave Berard
Senior Product Manager, Constant Contact
Developer Portal

View API documentation, code samples, get your API key.

Visit Page

Constant Contact 2020 End of Summer Community Sweepstakes!

The Constant Contact User Community is hosting a sweepstakes. The more you participate, the more chances you have to win! Read on to learn more...

Read More
Featured