About Aarron_G

Aarron_G · ‎10-07-2024

For over 3 years, we have considered creation of new V2 API Keys to be unsupported, as noted within our V2 API documentation. The 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. While this is an initial step, no timeline has yet been determined for full retirement of our V2 API. Further steps towards deprecation will be communicated when they are determined. Presently, existing applications can continue to utilize our V2 API.

Aarron_G · ‎08-23-2024

Hello @ShaunB, Thank you for reaching out to Constant Contact API Developer Support. I appreciate your bringing this to our attention, and I'm sorry for the inconvenience caused by the unexpected downtime for this tool. We believe that this issue has been resolved. Please let us know if you encounter any further error messages when attempting to get an access token through the V2 API Tester. Regards,

Aarron_G · ‎08-16-2024

On Monday, Aug. 19th, between approximately 6:00 and 6:30 AM ET, Constant Contact will be conducting maintenance. All legacy API requests (i.e., any requests to the api.constantcontact.com domain), will be unavailable during this time - please avoid their usage during this time frame, including any scheduled sync jobs. Our current V3 API (using the api.cc.email domain) will not be affected by this maintenance. Thank you in advance for your patience.

Aarron_G · ‎05-10-2024

Constant Contact has rebuilt and redesigned our events marketing tool! Our new events tool is being referred to as "Events 2.0", and we're now referring to the long-standing tool as "Legacy Events". Our Legacy Events tool is in the process of being retired, which has been communicated to Constant Contact users who were actively utilizing the tool, with the following timeline: On April 1st, 2024, existing legacy events became "read-only." It is no longer possible to create new legacy events or use the copy functionality for existing legacy events. Effective June 1st, 2024, the Legacy Events tool will be retired from our product completely. The event management endpoints available via our v2 API only support the Legacy Events tool. The v2 API itself has been considered a legacy tool for several years, and as such, has not received development related to new Constant Contact tools or features. Any POST or PUT requests made to Events endpoints via our v2 API currently return an HTTP 400 response, with the error key "http.status.gone". Effective June 1st, GET requests made to v2 API Events endpoints will return the same error response. We plan to add event management endpoints to the v3 API, supporting the Events 2.0 tool only, however a specific timeline for the new endpoints is not yet available. Information on any new endpoints will be added to the Release Notes section of our v3 API documentation. Information about the differences between the two tools and the retirement of Legacy Events can be found in these articles from our Knowledge Base & Community: Legacy Events versus Events 2.0 Events 2.0 and Legacy Event Retirement FAQ

Aarron_G · ‎05-03-2024

Hello @TylerA400, Thank you for reaching out to Constant Contact API Developer Support. I can confirm that, at least for the example given, there isn't an issue with the campaign_activity_id you're using - the referenced activity does have the primary_email role. The issue instead appears to be with the name of the property in your request body. The property name should be "scheduled_date", rather than "scheduled_date_time". If you still experience issues after modifying the property name, please let us know. Regards,

Aarron_G · ‎05-03-2024

Hello @TylerA400 , Thank you for reaching out to Constant Contact API Developer Support. I can confirm that, at least for the example given, there isn't an issue with the campaign_activity_id you're using - the referenced activity does have the primary_email role. The issue instead appears to be with the name of the property in your request body. The property name should be "scheduled_date", rather than "scheduled_date_time". If you still experience issues after modifying the property name, please let us know. Regards,

Aarron_G · ‎03-06-2024

Hello @KelseyT4, Thank you for reaching out to Constant Contact API Developer Support. There appears to have been an intermittently increased rate of '500 Internal Server Error' responses from our v3 API, between roughly 11:00 AM and 1:00 PM ET, though the issue currently appears to be resolved. If you're continuing to receive 500 responses from our v3 API, please let us know, along with timestamps if possible. We apologize for any inconvenience this caused, and thank you for your patience. Regards,

Aarron_G · ‎02-08-2024

Hello @OCA212, The issue was resolved as of approximately 11:20 PM ET last night, Feb. 7th. If you receive any further 500 responses past that point, please reach out to us via email, at webservices@constantcontact.com, with as much information as possible (the API key you're using, time stamps, example requests & responses, etc.), so that we can investigate. Thank you again for your patience.

Aarron_G · ‎02-08-2024

As of approximately 11:20 PM ET, Feb. 7th, this issue has been resolved. Our V3 API and Developer Portal are available and operating normally. Thank you again for your patience.

Aarron_G · ‎02-08-2024

Hello @user292613, This issue was resolved as of approximately 11:20 PM ET last night (Feb. 7th). Any 500 responses you received after that point do not appear to be related to yesterday's production issue. If you're still experiencing issues, please reach out to us via email, at webservices@constantcontact.com, with as much information as possible (the API key you're using, time stamps, example requests & responses, etc.), so that we can investigate. Regards,

Aarron_G · ‎02-07-2024

Beginning from roughly 5:00 AM ET today (Feb. 7th, 2024), we are experiencing an issue which is causing most requests made via our V3 API to result in a '500 Internal Server Error' response. Additionally, most attempts to access the 'My Applications' page within the V3 Developer Portal are also resulting in an error ("You've encountered an error! Sorry about that. Please try again in a few minutes."). We apologize for any inconvenience this causes, and will update this thread as we know more. Thank you for your patience.

Aarron_G · ‎01-24-2024

Beginning from roughly 12:55 PM ET today (Jan. 24th, 2024), we experienced an intermittent issue which caused some requests made via our V3 API to result in a '500 Internal Server Error' response. As of approximately 2:40 PM ET, this issue has been resolved; our V3 API is available and operating normally. We apologize for any inconvenience this caused, and thank you for your patience while service was restored.

Aarron_G · ‎11-22-2023

As of approximately 12:35 AM ET, Nov. 22nd, this issue has been resolved. Our V3 API and Developer Portal are available and operating normally. Thank you again for your patience.

Aarron_G · ‎11-21-2023

Beginning from roughly 11:30 AM ET today (Nov. 21st, 2023), we are experiencing an issue which is causing most requests made via our V3 API to result in a '500 Internal Server Error' response. Additionally, most attempts to access the 'My Applications' page within the V3 Developer Portal are also resulting in an error ("You've encountered an error! Sorry about that. Please try again in a few minutes."). We apologize for any inconvenience this causes, and will update both our status page and this thread as we know more. Thank you for your patience.

Aarron_G · ‎06-13-2023

This issue has been resolved; our public API is now available and operating normally. Thank you for your patience.

Aarron_G · ‎06-13-2023

There is currently a widespread AWS outage affecting several components of the Constant Contact suite. This includes requests made to our public API, which may return '503 Service Unavailable'. This issue is not specific to Constant Contact, but we are monitoring the situation and will provide updates as we know more.

Aarron_G · ‎05-12-2023

On Saturday, May 20th, between approximately 8:30 pm and 9:30 pm ET, we will be doing network maintenance. Please avoid usage of our API during this time frame - including any scheduled sync jobs. Thank you in advance for your patience.

Aarron_G · ‎05-03-2023

Constant Contact has considered use of the TLS v1.1 protocol with our V2 API unsupported since September 30th, 2018. Beginning on May 16th, 2023, we will fully disable use of TLS v1.1 with the V2 API. All clients requesting connections with our V2 API will need to use the TLS v1.2 protocol. Clients using TLS v1.1 will not be able to connect to our API servers. This change does not affect our V3 API, which already requires the use of TLS v1.2 or higher. For further details, please visit our original Tech Blog article from 2018. Regards,

Aarron_G · ‎04-07-2022

Hello @adenisoncmnh, Thank you for reaching out to Constant Contact API Developer Support. I am sorry for the slightly extended response time. We've found that the issue which caused these campaigns to fail to send was not related to the campaigns themselves or your usage of our API in any way; the issue was instead account related. We've replied to you via email with further details, but wanted to close the loop here as well. If you haven't received our reply, please contact us at webservices@constantcontact.com and reference case number 29686429. While unrelated to the issue you inquired about, we can confirm that our V2 API has not been deprecated. That said, we do encourage users to begin migrating their applications to our current V3 API as soon as possible. The V2 API will be retired at some point, though that timeline has not yet been decided. A Quick Start Guide for our V3 API can be found here, and the rest of the V3 API documentation can be accessed from this page: Constant Contact V3 API Quick Start Guide Please let us know if you have any further questions! Regards,

Aarron_G · ‎03-22-2022

Constant Contact will be conducting maintenance on our V3 API beginning today, March 22nd, at approximately 1:30 PM ET and ending at approximately 1:30 PM ET tomorrow, March 23rd. During this time period, any applications/integrations which have not yet been updated to use our new authorization management service (as documented here https://developer.constantcontact.com/api_guide/auth_update_apps.html) will receive a 401 Unauthorized error response to any requests made to our V3 API. The following categories of applications will be unaffected: - V3 applications which have been updated to use our new authorization service - V3 applications registered since Feb. 10th - Applications using our V2 API Thank you in advance for your patience. For all applications affect by this maintenance, please note: Our previous V3 API authorization management service will no longer be available as of March 31st. If you have any questions about updating your application, please contact our API Support team at webservices@constantcontact.com

Aarron_G · ‎03-10-2022

Constant Contact will be conducting maintenance on our V3 API today, March 10th, from approximately 1:00 PM to 3:00 PM ET. During this time period, any applications/integrations which have not yet been updated to use our new authorization management service (as documented here) will receive a 401 Unauthorized error response to any requests made to our V3 API. The following categories of applications will not be affected: V3 applications which have been updated to use our new authorization service V3 applications registered since Feb. 10th Applications using our V2 API Thank you in advance for your patience. For all applications affected by this maintenance, please note: Our previous V3 API authorization management service will no longer be available as of March 31st. If you have any questions about updating your application, please contact our API Support team at webservices@constantcontact.com

Aarron_G · ‎02-11-2022

Hello @KatherineG1840, Please note that Postman is not built or supported by Constant Contact, so we are limited in the support we can provide, but will try to answer any questions to the best of our ability. The "invalid_request" error you're encountering when using the Implicit Flow is due to the lack of the required nonce parameter. Postman doesn't appear to offer a dedicated field for this parameter; I was able to find the following open feature request, asking them to add one: OAuth2 supporting a nonce for the auth URL. A workaround would be to manually append the nonce parameter to the authorization endpoint URL: Regarding the error you encountered when using the Authorization Code Flow, you'll notice that our token endpoint expects the authorization_code as a query parameter & your app's credentials in the Authorization header. Postman is sending the authorization_code in the request body, and I was unable to locate an option within Postman to send it as a query parameter instead. I was able to successfully obtain an access token by switching Postman's Client Authentication option from "Send as Basic Auth header" to "Send client credentials in body", however this isn't a documented, supported method of using our token endpoint, so I can't guarantee this will always be a viable workaround. I'd recommend contacting Postman's support to check if they offer a way to send the authorization_code as a query parameter. Please let us know if you have any questions! Regards,

Aarron_G · ‎02-01-2022

Hello @AndreaL3758, This post appears to be following up on your previous post, found here: https://community.constantcontact.com/t5/Developer-Support-ask-questions/creating-contact-with-custom-field-using-API-v3-not-working/m-p/381385 Thank you for providing the full error response you're receiving. The error is consistent with the solution provided in the other thread. For reference, I'm including that solution here: @John__B wrote: The full format of the error is "custom_fields.{custom field name} is missing". In this instance, the name of the custom field associated with the custom_field_id you provided is "id". Based on the request body you provided it looks like the error is being caused by the “value” property being capitalized in your request when our system is expecting the property in lower case. I am including documentation on the full request which includes a body sample below: PUT (update) a Contact: https://developer.constantcontact.com/api_reference/index.html#!/Contacts/putContact Please have a look and let us know if you have any other questions! Regards,

Aarron_G · ‎01-07-2022

Hi Tyler, You're very welcome! While I haven't yet completed troubleshooting, I should have an update for you early next week.

Aarron_G · ‎12-22-2021

Hello @TylerC391, Thank you for reaching out to Constant Contact API Developer Support. I've been able to replicate the response you're receiving, and suspect that the issue is related to the request's Content-Type and/or Content-Length. I'll be conducting some further troubleshooting, and will update this thread with any findings. Regards,

Aarron_G · ‎12-11-2021

As of 2:35 AM ET, Dec. 11th, this issue has been resolved. Our V3 API and login to Constant Contact via SSO are available and operating normally. Thank you again for your patience.

Aarron_G · ‎12-10-2021

Beginning from roughly 8:20 PM ET today (Dec. 10th, 2021), we are experiencing an issue with our website which may result in our V3 API and login to Constant Contact via SSO (Single Sign On) being unavailable. We apologize for any inconvenience this causes, and will update both our status page and this thread as we know more. Thank you for your patience.

Aarron_G · ‎12-08-2021

The AWS outage which was affecting our V3 API service has been resolved. The impaired AWS service began to recover around 8:45 PM ET Dec. 7th. Thank you again for your patience and we apologize for any inconvenience this may have caused.

Aarron_G · ‎12-07-2021

We've determined that this issue is related to a widespread Amazon Web Services (AWS) outage, affecting several components of the Constant Contact suite. The outage is not specific to Constant Contact, but we are monitoring the situation and will update this thread, as well as our Status Page, as we know more. Thank you for your patience.

Aarron_G · ‎11-11-2021

Hello @user4960333, We've sent a reply to your email with additional details. Please let us know if haven't received it. Regards,

About Aarron_G

Creation of V2 API Keys Has Been Retired

Re: API Returns Forbidden

COMPLETED - API Maintenance Notification - Aug. 19...

Retirement of Legacy Events tool

Re: Unknown Date/Time Error when creating an Email...

Re: Unknown Date/Time Error when creating an Email...

Re: Constant Contact Down?

Re: Production Issue Notification - Feb. 7th, 2024

Re: RESOLVED - Production Issue Notification - Feb...

Re: Production Issue Notification - Feb. 7th, 2024

RESOLVED - Production Issue Notification - Feb. 7t...

RESOLVED - Production Issue Notification - Jan. 24...

Re: Production Issue Notification - Nov. 21st 2023

RESOLVED - Production Issue Notification - Nov. 21...

Re: Production Issue Notification - June 13th 2023

Production Issue Notification - June 13th 2023

Network Maintenance Notification

Disabling TLS v1.1 for V2 API - Immediate Action R...

Re: Dozens of failed email campaigns, no response ...

V3 API Maintenance Notification - March 22nd & 23r...

V3 API Maintenance Notification - March 10th, 2022

Re: v3 API and Postman OAuth

Re: error saying custom field is missing, but it i...

Re: Request body for Importing contacts with CSV f...

Re: Request body for Importing contacts with CSV f...

Re: Production Issue Notification - Dec. 10th 2021

Production Issue Notification - Dec. 10th 2021

Re: Production Issue Notification

Re: Production Issue Notification

Re: blank screen coming while user trying signing ...