V2 Campaigns API: Caught exception while calling remote EJB

[AnalyticsEdge]

Started getting these errors for multiple accounts a few days ago. A typical API call is:

https://api.constantcontact.com/v2/emailmarketing/campaigns/{campaign_id]/tracking/clicks?api_key=.....

The error is:

400 Bad Request 
 [{"error_key":"http.status.bad_request","error_message":"Caught exception while calling remote EJB; nested exception is com.roving.RovingRuntimeException: TrackingAPIClient.callContactsAPI() error, site owner=..."}]

Any idea what is going on?

[MarketingC731]

We are also having clients report this error and can duplicate on our own deployment. Our first report was May 10th.

Has there been some form of change to the existing V2 deployment?

[AnalyticsEdge]

I escalated to webservices. confirmed problem. they are working on it. no ETA.

[John__B]

Hello AnalyticsEdge & MarketingC731,

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 greatly appreciate you bringing this issue to our attention. This issue is intermittently affecting the V2 Email Campaign Tracking endpoints. I apologize for any inconvenience this has caused. We have reported it to our engineering team who is in the investigation process for a resolution. While I’m unable to provide an ETA for when a resolution will be reached at this time, we will be sure to notify you as soon as we have any updates.

Please let us know if you have any other questions in the meantime.

Regards,

[SyncApps-Expert]

Hey John, it has now been weeks. Have you deprecated your V2 API and not told anyone about it yet? 48 hours I get, but 3 weeks seems quite suspect here.

[John__B]

Hello SyncApps-Expert,

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 can confirm that we are still working to mitigate this issue and that the legacy V2 API has not yet been deprecated. I would note that 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). 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, and strongly recommend upgrading to the V3 API to ensure you're ahead of the curve. Currently, we've already retired the V2 endpoint for Custom Code email creation, as it used an outdated version of our Custom Code editor that has been retired.

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,

[SyncApps-Expert]

Thanks, John, and I have updated our SyncApps subscribers today. Thanks again for the heads-up.

[John__B]

Hello AnalyticsEdge, MarketingC731 and SyncApps-Expert,

I am pleased to inform you that the issue regarding intermittent 400 error responses from the legacy V2 API email campaign tracking endpoints has been resolved. We apologize for the inconvenience caused by this issue and greatly appreciate your patience as we worked toward its resolution.

Please let us know if you have any questions.

Regards,