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.

No Longer Able To Send Contacts From Our Production Environment via API

SOLVED
Go to solution
Highlighted
Occasional Contributor

No Longer Able To Send Contacts From Our Production Environment via API

Hi, we have had an integration in place for some time now.  Wesend contacts using the CreateAddContactsActivity method.  It has been working perfectly up until the last week or so.  Now, the system sends the information, but it never appears in our constant contact account.  As well, if we try sending from our test environment it works fine.  What is also strange is there are no errors being thrown.  We do have a number clients that use this integration.  I would appreciate someone looking into this ASAP.

 

Thanks,

 

Cory

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Employee

Re: No Longer Able To Send Contacts From Our Production Environment via API

Just a quick follow up one this: I worked with Cory to figure out the issue. Our API traffic service (Mashery) stopped allowing RC4 ciphers, which Cory's server was using. Upgrading the server on their side to use a new security cipher (probably AES) solved the issue.

 

Anyone using Windows Server 2003 may have experienced this, and should upgrade their server to use a newer cipher to solve issues where they're not able to connect to us.

 

We apologize for the inconvenience; this change caught us unaware, or we would have communicated this out to our developers bfore the change took place.

 

Best Regards,

Shannon Wallace

Partner API Support Engineer

View solution in original post

1 REPLY 1
Highlighted
Employee

Re: No Longer Able To Send Contacts From Our Production Environment via API

Just a quick follow up one this: I worked with Cory to figure out the issue. Our API traffic service (Mashery) stopped allowing RC4 ciphers, which Cory's server was using. Upgrading the server on their side to use a new security cipher (probably AES) solved the issue.

 

Anyone using Windows Server 2003 may have experienced this, and should upgrade their server to use a newer cipher to solve issues where they're not able to connect to us.

 

We apologize for the inconvenience; this change caught us unaware, or we would have communicated this out to our developers bfore the change took place.

 

Best Regards,

Shannon Wallace

Partner API Support Engineer

View solution in original post

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