About John__B

Hello Wilard,   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.   It looks like we've already followed up with you directly via email, but I wanted to close the loop here as well. If you haven't received our reply, please let us know via email at webservices@constantcontact.com, and reference case number 29879999. Please have a look and let us know if you have any other questions! Regards, ... View more

Hello user7446451,   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.   After reviewing the login URL you provided, we were able to determine that the reason the URL did not properly redirect to the login page is due to a period character (.) in your state parameter value. We have documented this behavior and passed it up to our development team to review and update our documentation. I apologize for any inconvenience this may cause. We do know that the following character types will work in the state parameter value:    Alphanumeric Comma Underscore Hyphen   Removing the period from the state parameter value should allow you to successfully reach the login page and grant access to your application.   Please let us know if you have any other questions!   Regards, ... View more

Hello RyanM244,   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.   Upon reviewing our logs for your keys, I found multiple instances of successful refresh token requests being made and then another refresh token request being made with the previous/expired refresh token, resulting in the “The refresh token is invalid or expired” error response you’ve encountered. It appears that when these successful refresh token requests are being made, the new refresh token is not being stored in your application for the next refresh token request.    When a refresh token is used, it becomes invalid and the new refresh token you received would need to be used for the next refresh request. This does not invalidate the existing/previous access token which will continue to be valid for the duration of its lifespan.    The Long Lived Refresh Tokens option does indeed work. When this option is selected, your refresh tokens would continue to be valid after you exchange them for a new access token. Because the original refresh token will continue to work, you will not receive a new refresh token when you refresh the access token.   Please let us know if you have any other questions!   Regards, ... View more

Hello MarketerL5795,   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.   A Client Credentials flow is one of several options we’re investigating for future updates to help accommodate non-interactive integrations. While I’m unable to provide an ETA or specifics for future updates at this time, we’ll be sure to notify our users about these types of updates when they occur. You can keep an eye on our documentation for these types of announcements: https://v3.developer.constantcontact.com/api_guide/release_notes.html   Please let us know if you have any other questions!   Regards, ... View more

Hello NateP57,   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.   While we don’t have any updates on an alternate flow for unattended/non-interactive API integrations at this time, we are still investigating several options for future updates to help accommodate these types of integrations while also maintaining account security.   Please let us know if you have any other questions!   Regards, ... View more

Hello AnthemUnited,   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.   It looks like we've already followed up with you directly via email, but I wanted to close the loop here as well. If you haven't received our reply, please let us know via email at webservices@constantcontact.com, and reference case number 29580609.   Please have a look and let us know if you have any other questions!   Regards, ... View more

Hello SegmintD, HeidiS146 &WCCGoldenApple,   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 the Content-Type header did change with the update to our new authorization service. For POST requests to the https://authz.constantcontact.com/oauth2/default/v1/token endpoint, the Content-Type header value should be: “application/x-www-form-urlencoded”.    The Accept header value for this request should be: “application/json”.   Examples of both headers can be found under the Example Request section of step 4 (Get the Access token and Refresh token) on the Authorization Code documentation which I’ll link to below.   Get the Access and Refresh Token: https://v3.developer.constantcontact.com/api_guide/server_flow.html#step-4-get-the-access-token-and-refresh-token   Please have a look and let us know if you have any other questions!   Regards, ... View more

Hello MKTG_Team,   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.   After reviewing the logs for your keys, I found that the grant_type value being used in your token requests is “client_credentials”. If you are trying to use the authorization code flow, the required grant_type is “authorization_code”.   Our access tokens expire after 1440 minutes (86,400 seconds) but your application can utilize refresh tokens to extend the lifespan of an access token by exchanging it for a new set of access and refresh tokens. For more information on this process I am including overview documentation for our OAuth2 authentication and the Authorization Code flow below.   OAuth2 Overview: https://developer.constantcontact.com/api_guide/auth_overview.html   Authorization Code Flow: https://developer.constantcontact.com/api_guide/server_flow.html   Please have a look and let us know if you have any other questions!   Regards, ... View more

Hello user100785,   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 had some scheduled maintenance around the time that you posted this, which may have affected being able to edit and create V3 applications within the My Applications page. All should be working as expected now.   Developer Community Notice RE: V3 API Maintenance Notification - March 22nd & 23rd, 2022 https://community.constantcontact.com/t5/Authentication-and-Access-ie-401/V3-API-Maintenance-Notification-March-22nd-amp-23rd-2022/m-p/384798   We apologize for the short notice of the maintenance window. Due to the approaching deadline for the retirement of our previous authorization service, we had to move quickly on the required system maintenance. Please let us know if you have any other questions!   Regards, ... View more

Hello JohnR8516, ZainabL0 & SDC1715,   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 the behavior you encountered of not being able to edit existing V3 applications/keys on 03/23 was part of our scheduled maintenance on 03/22 & 03/23. I apologize for any inconvenience this may have caused as I understand how important it is that our users have access to edit their applications.   Developer Community Notice RE: V3 API Maintenance Notification - March 22nd & 23rd, 2022 https://community.constantcontact.com/t5/Authentication-and-Access-ie-401/V3-API-Maintenance-Notification-March-22nd-amp-23rd-2022/m-p/384798   We apologize for the short notice of the maintenance window. Due to the approaching deadline for the retirement of our previous authorization service, we had to move quickly on the required system maintenance. We appreciate your feedback about our maintenance notifications being more specific in what functionality will be affected during these periods. Your feedback and experience is essential to improving our product, so thank you for reaching out to us regarding this matter.   Please let us know if you have any other questions!   Regards, ... View more

Hello user816630,   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 the V2 API authentication endpoints will continue to function past the end of this month. That being said, while our V2 API endpoints are currently functional, they are considered legacy and we do plan to deprecate them. I would highly recommend migrating your application to our V3 API which I am linking quick start and migration guides for below.   V3 API Quick Start Guide: https://developer.constantcontact.com/api_guide/getting_started.html   V2 to V3 Data Migration Overview: https://developer.constantcontact.com/api_guide/migration_overview.html   Please have a look and let us know if you have any other questions!   Regards, ... View more

Hello JuneL4,   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.   After reviewing the logs for your key, it appears that the reason you are encountering the “Client authentication failed” error response is because your client_id & client_secret have not yet been Base64 encoded in the Authorization header of the token request. This request requires basic authentication for the string “client_id:client_secret”.    In Postman, this can be entered in the authorization tab of the request with the authorization type set to “Basic Auth”. The username would be the client_id and the password would be the client_secret. Below I am including documentation for the access and refresh token request. I would recommend reviewing the section titled “Authentication” for more information about the basic authentication requirement.   Get the Access and Refresh Token: https://v3.developer.constantcontact.com/api_guide/server_flow.html#step-4-get-the-access-token-and-refresh-token   Please have a look and let us know if you have any other questions!   Regards, ... View more

Hello AlanJ7943,   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.   Everything that you mentioned is definitely possible with Constant Contact. Contact lists can be created or deleted at any time. In terms of the example you provided with all new customers receiving an offer email once and then continuing to receiving other relevant event driven emails, you could utilize an automated email series with a list-join trigger. Once a contact is added to a list connected to an automated series in this way, they would receive a series of emails that you add in the order and delay periods that you configure in the series settings. Below I’m including a detailed support article with more information about automated email series:   Create an Automated Email Series: https://knowledgebase.constantcontact.com/articles/KnowledgeBase/27935-Choosing-a-Trigger-for-Your-Automated-Email-Series   In terms of our API, you could utilize various endpoints to add or delete contacts and contact lists. Below I’m including a quick start guide for our V3 API as well as our documentation on some of these endpoints.   V3 API Quick Start Guide: https://developer.constantcontact.com/api_guide/getting_started.html   Import Contacts Using a CSV File: https://developer.constantcontact.com/api_reference/index.html#!/Bulk_Activities/contactsCSVImport   Import Contacts Using JSON Payload: https://developer.constantcontact.com/api_reference/index.html#!/Bulk_Activities/bulkImportContactsJSON   Delete Contacts in Bulk: https://developer.constantcontact.com/api_reference/index.html#!/Bulk_Activities/postContactDelete   POST (Create) a List: https://developer.constantcontact.com/api_reference/index.html#!/Contact_Lists/createList   Delete a List: https://developer.constantcontact.com/api_reference/index.html#!/Contact_Lists/deleteListActivity Please have a look and let us know if you have any other questions!   Regards, ... View more

Hello MatthewR8221,   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.   It looks like we've already followed up with you directly via email, but here is the information provided for visibility on the forum:   After reviewing the authorization request URL you provided, we were able to determine that the reason the URL did not properly redirect to the login page is due to period characters (.) in your state parameter value. We have documented this behavior and passed it up to our development team to review and update our documentation. I apologize for any inconvenience this may cause. We do know that the following character types will work in the state parameter value:    Alphanumeric Comma Underscore Hyphen   Removing the periods from the state parameter value should allow your users to properly reach the login page and grant access to your application.   Please have a look and let us know if you have any other questions!   Regards, ... View more

Hello DanielH547,   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.   The primary reason that the Contact ID is used as the identifier when updating or deleting a contact rather than the email address is because it allows for the ability to update/change a contact’s email address and maintain the engagement history of the contact itself.     Please let us know if you have any other questions!   Regards, ... View more

Hello Ann,   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.   Constant Contact does not currently offer a way to connect with NetSuite; however, I was able to find a 3rd party integration online developed by Cazoomi which I’ll provide a link to below.   Cazoomi NetSuite and Constant Contact Integration: https://www.cazoomi.com/syncapps/netsuite-to-constant-contact/   Cazoomi Support: https://support.cazoomi.com/hc/en-us   Please have a look and let us know if you have any other questions!   Regards, ... View more

Hello @WCCGoldenApple , @QgivP & @user915548,    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 to our attention. We have been able to replicate the invalid scope responses you have received when encoding the scopes portion of the authorization request URL. I’m going to bring this to our development team for further investigation and update our documentation accordingly. In the meantime, we have found through testing that excluding the scopes portion of the URL from being encoded so the “+” characters generate as “+” and not “%2B” will allow the authorization request to be successful.    Please let us know if you have any other questions!   Regards, ... View more

Hello RTX,   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.   To get started with the V3 API, you’ll want to start by going through the V3 API Authorization Code Flow. Please note, after step 1, you should set up step 4 before proceeding, because the authorization code from steps 2 and 3 only has a lifespan of 300 seconds. The Authorization Code Flow’s documentation also has PHP examples for the Authorization, Access & Refresh token requests .   In step one of the V3 API OAuth2.0 Authorization Code Flow, you’ll want to set up your “redirect_uri” so that after a client grants permission via the Authorization Request URL, Authorization Service can send the user to a webpage that you specify, and also send the Authorization Code back to your application so that it can complete the Authentication process.   V3 API OAuth2.0 Authorization Code Flow https://v3.developer.constantcontact.com/api_guide/server_flow.html   V3 API OAuth2.0 Overview https://developer.constantcontact.com/api_guide/auth_overview.html   Once you have your first set of tokens, you’ll want to set the access token and the refresh token as values for corresponding variables in your application, so that when your program runs through step 8 of the OAuth2.0 Authorization Code Flow to get the new set of tokens it can assign new values to those variables to maintain an authenticated connection.   V3 API - Refresh the Access Token https://v3.developer.constantcontact.com/api_guide/server_flow.html#step-8-refresh-the-access-token   I’m also including documentation on our sign-up form endpoint that you can use to add or update contacts through the form you are developing.   V3 API Sign-up Form Endpoint: https://developer.constantcontact.com/api_reference/index.html#!/Contacts/createOrUpdateContact   Please have a look and let us know if you have any other questions!   Regards, ... View more

Hello JoeD576,   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.   As Constant Contact rate limits the token endpoint, it is recommended that you only send in the refresh token to obtain a new access token when your existing access token is expired or about to expire. You are correct in that our access tokens have a maximum life of 24 hours. A 429 response indicates that the rate limit has been reached at the token endpoint. For more information on our access and refresh tokens, I am including documentation below.   OAuth 2.0 Overview: https://developer.constantcontact.com/api_guide/auth_overview.html   Please have a look and let us know if you have any other questions!   Regards, ... View more

Hello TACmarketing,   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.   It looks like @josephineo already came up with the solution in an above comment but based on your response, it looks like the only scope included in your authentication request was the  “contact_data” scope. In order to obtain a refresh token the “offline_access” scope must also be included in the request. Below I am including the overview documentation for our available OAuth 2.0 flows.   OAuth 2.0 Overview: https://developer.constantcontact.com/api_guide/auth_overview.html   Please have a look and let us know if you have any other questions!   Regards, ... View more

Hello AfshinY,   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.   It looks like we've already followed up with you directly via email, but I wanted to close the loop here as well. If you haven't received our reply, please let us know via email at webservices@constantcontact.com, and reference case number 29531377.   Regards, ... View more

Hello AfshinY,   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.   It looks like we've already followed up with you directly via email, but I wanted to close the loop here as well. If you haven't received our reply, please let us know via email at webservices@constantcontact.com, and reference case number 29531377.   Regards, ... View more

Hello FirstNameL10197,   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.   Based on reports from other Gravity Forms users in the community, Gravity Forms has released an update since this post addressing our new authentication flow which should now allow you to successfully connect the plugin with your Constant Contact account. Below I’m including a link to Gravity Forms’ manual update instructions.    Gravity Forms Manual Update Instructions: https://docs.gravityforms.com/how-to-manually-update/   Gravity Forms Plugin Constant Contact Change Log: https://docs.gravityforms.com/constant-contact-change-log/   Please have a look and let us know if you have any other questions!   Regards, ... View more

Hello MarcT88,   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.   Based on your most recent reply in this thread, it sounds like the Gravity Forms plugin is now connecting properly for you after the developer released their most recent update.   Please feel free to post here or reach out to us directly at webservices@constantcontact.com if you continue to experience any issues or have any additional questions.    Regards, ... View more

Hello DanielH547,   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.   The list of valid activity types that can be returned in the Get Contact Activity Details request is as follows:   em_sends - Send activities em_opens - Email open tracking activities em_clicks - Link click-through tracking activities em_bounces - Bounce tracking activities em_optouts - Opt-out tracking activities em_forwards - Forward to a friend tracking activities   These activity types are also listed towards the top of the reference documentation for the Get Contact Activity Details request.   GET Contact Activity Details: https://v3.developer.constantcontact.com/api_reference/index.html#!/Contacts_Reporting/getContactTracking   Please have a look and let us know if you have any other questions!   Regards, ... View more

Hello AvromFinkelsteinF,   Thank you for reaching out to Constant Contact API Developer Support.   We appreciate your feedback regarding this error message. I’m going to bring this to our development team and see if we can update the verbiage to reflect that wildcard characters are supported at the lowest level subdomain.   Please let us know if you have any other questions!   Regards, ... View more

Hello TylerC391,   We greatly appreciate your continued patience and I’m sorry for the delay in our response. Aarron has continued to assist an internal team with a project that has taken up most of his bandwidth but he does plan to continue troubleshooting this issue with you as soon as possible.   We appreciate the additional information you have provided regarding your colleague’s successful multipart post using a Python implementation. If you have any other questions or concerns in the meantime, please feel free to post here or reach out to us directly via email at webservices@constantcontact.com.   Regards, ... View more

Hello JenniferS1215,   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 noticed that you also reached out to us directly via email and we have followed up with you through that channel. Since you had some additional questions, we’ll continue our communication via email.    Regards, ... View more