About Aarron_G

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, ... View more

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, ... View more

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, ... View more

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

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, ... View more

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. ... View more

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. ... View more

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. ... View more

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

Hello Pramod, While Constant Contact does not directly provide or support any Drupal modules, search results on drupal.org do appear to show other third-party modules available which support Drupal 8.   If you're able to add Javascript directly to your site, another option would be to use a Constant Contact Inline or Pop-Up Sign-Up form, rather than any Drupal module.   If our own sign-up forms don't quite meet your needs, it may be possible to collect sign-ups using a form created through Drupal, then use a 3rd party such as Zapier to add the contact to your Constant Contact account.   Hopefully one of these options will meet your needs!   Regards, ... View more

Hello,   We've followed up via email. Please let us know if the email hasn't been received. Thank you! ... View more

Hello,   I see that you've also contacted us on this via email. We've replied to your email, but I wanted to close the loop here as well. If you haven't received our reply, please let us know at webservices@constantcontact.com, and reference case number 28832010.   Regards, ... View more

Maintenance has been completed and the V3 API is back online. ... View more

Hello @DonnaP4507, I see that you've also contacted us on this issue via email, which we've replied to, however I wanted to close the loop on this post as well. The endpoint path you provided includes an extra segment. The correct endpoint is: https://api.cc.email/v3/reports/email_reports/{campaign_activity_id}/tracking/bounces The documentation for this endpoint can be referenced here: https://developer.constantcontact.com/api_reference/index.html#!/Email_Reporting/getBounces   Please let us know if you have any questions!   Regards, ... View more

Hello @MichelleH240,   In order to fully troubleshoot, would you please send us an email at webservices@constantcontact.com with the following information?  Your API key The code you're using / API calls you're making Which step of the authorization flow is returning this error The login username of the Constant Contact account you're attempting to generate a token for, if the issue seems to be limited to a specific account Regards, ... View more

Hello @LewisS, Your speculation is correct, the format_type property used when creating an email campaign via our v3 API does control whether the campaign is created in the format used by our legacy custom code editor (format_type 1) or our modern custom code editor (format_type 5). As you noted, users of our website interface are no longer able to edit or schedule campaigns that are in the legacy format; they are only able to copy them into the modern format. This change was initially made last month, but was temporarily rolled back. It was re-implemented a few days ago. It is still possible to schedule campaigns in the legacy format using the v2 API, however the v2 API does not have the ability to create email campaigns in the modern custom code format. Our development and implementation of newer features is focused on the v3 API, as the current version. If you do need to continue with a mixed workflow (creating campaigns via the API, scheduling via the website), the best solution would be to migrate your integration to the v3 API. You are also correct that, in the modern custom code editor, square brackets are not supported within the subject line. Square brackets are reserved due their use in Subject Line Personalization, which was not available in the legacy custom code editor. While I'm unable to estimate when or if support for brackets in the subject line could be added, we do have an open feature request, and I've added your account's interest to that request. Please let us know if you have any questions. Regards, ... View more

Hello @DanielleN22,   Issues at this step in the flow are commonly due to either the authorization code having expired (it is valid for 60 seconds) or issues with the Authorization header.   To set up your Authorization header, you'll need both your app's client_id (which is your API key) and your client_secret. You would put these values in the following format: "client_id:client_secret", then convert that string to Base 64 encoding. The result is used in the Authorization header. An example would look like: Authorization: Basic MjdlOPBkNjktUmQ4MY00MGUwLWVmZmYtODRjZjM2   If you're still experiencing issues after checking those two items, you can send us your code for review via email, at webservices@constantcontact.com.   Regards, ... View more

Hello @SmithArchives,   As the Drupal module you referenced was not developed by Constant Contact, reporting the issue on the module's project page (as you've done) would be the best route to obtain support. That said, I see that the Drupal 7 version of that module was built using our v1 API. Our v1 API has been deprecated and we are no longer offering support for it, outside of fixing critical bugs. While our v1 endpoints are currently still functional, we are moving towards fully disabling the v1 API (no set timeline is currently available).   My recommendation would be to consider alternatives to the Drupal 7 version of that module. The module's project page does include a version which has been rebuilt using our v2 API, however that version appears to require Drupal 8. I've also found the following module, built on our current v3 API, but it requires Drupal 8.8 or higher: https://www.drupal.org/project/ik_constant_contact   If you're able to add Javascript directly to your site, another option would be to use a Constant Contact Inline or Pop-Up Sign-Up form, rather than any Drupal module.   If our own sign-up forms don't quite meet your needs, it may be possible to collect sign-ups using a form created through Drupal, then use a 3rd party such as Zapier to add the contact to your Constant Contact account.   Hopefully one of these options will meet your needs! Regards, ... View more

Hello @RobertS0822,   Thank you for bringing this to our attention! The response is intended to include an error_key and error_message. I've reported this to our engineers, to be updated.   As you concluded, the 409 error response you received was due to your payload containing a name which was already in use by an existing campaign. As a general reference which may be useful to anyone that comes across this post, our documentation includes a glossary of HTTP response codes, which can be found here: https://developer.constantcontact.com/api_guide/glossary_responses.html   Regards, ... View more

Hello @RobertS0822,   Thank you for bringing this to our attention! The membership_count property is only returned if you pass in a query parameter, which is currently absent from the documentation. I'll look into having the documentation updated. For use in the meantime, the parameter name is "include_membership_count"; possible values are "all" and "active" (which only counts contacts in mailable statuses). Let us know if you have any questions!   Regards, ... View more