About Courtney_E

Hello user122953,   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'm sorry for the difficulty you’ve encountered regarding connecting the Magento integration.    This integration does not utilize our public API and is directly supported by our Tier 2 support team.   It looks like you've already spoken with a team member in greater detail regarding this, but if you have any follow up questions or concerns, please reach back out to our support team at 866-289-2101 and reference case #29558520. ... 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.   After taking a look at our logs for the key in use with your account, itI’m seeing that your attempts to refresh the token set are failing due an invalid refresh token being used (response:invalid_refresh_token), which is likely why you are not generating a new token value.   It looks like your key is using a Long Lived Refresh Token, so here are some things to double check:   -In step 8, the refresh token should remain the same in the response code as it was in your request, while a new access token should be generated. If you are saving these as variables, I’d check to make sure that the right values are being assigned to the right variables within your application.     -Each time you complete steps 1-4 of the OAuth2 Authorization Code Flow to connect a specific account (go through the whole flow again from the beginning), a new Refresh Token is assigned for that account’s authenticated connection and the old refresh token becomes invalidated.   You can also send us your example request/response code securely by email at webservices@constantcontact.com if you’d like us to look into this further with you.   Please have a look and let us know if you have any other questions!  ... View more

Hello AngelaB5449 ,   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 provide improved security, Constant Contact is now using a new authorization management service, and will be ending support for the previous service/keys on March 31, 2022. Based on reports from other Gravity Forms users in the community, Gravity Forms has recently released an update addressing our new authentication flow which should now allow you to successfully connect the plugin with your Constant Contact account. I’ll include the complete instructions below:   First, (if you haven’t already) you’ll start by copying your existing V3 API key to update it to the new authorization management service: -Login to Constant Contact -Navigate to: https://app.constantcontact.com/pages/dma/portal/  -Click the “copy” button to the far right of the API key you use for Gravity Forms -Close the “Successfully Copied” pop-up -If the “You need to update your applications” pop-up appears again, you can close it -You’ll now see a new section at the top of the “My Applications” page called “Valid Applications”  -In that section you’ll see the name/key value of the one we copied, with”(New)” after the name -Click the name of the new copied key to open it -All you need to do here is click the “Generate Secret” button to generate a new secret. -Copy the secret to save for a later step, because once you close that pop-up you won’t be able to access it again (though you can always generate a new one)   Otherwise, if you can’t access the original key, or are connecting for the first time and haven’t yet generated one, you can create a new key to use when updating your integration using steps 1 & 2 of the article below:   Create an Application Integration https://v3.developer.constantcontact.com/api_guide/apps_create.html   Next, you will need to update your Gravity Forms plugin in WordPress:   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/   Lastly, you will connect the updated plugin with the copied key’s new secret:   Setting Up the Gravity Forms Constant Contact Add-On https://docs.gravityforms.com/constant-contact-add-on/   Please note that Gravity forms is a 3rd party product and 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 as they pertain to Constant Contact’s API endpoints and functionality. Constant Contact makes these endpoints available for 3rd party developers to create integrations with our system.   Support » Plugin: Gravity Forms Constant Contact https://wordpress.org/support/plugin/gravity-forms-constant-contact/   Please have a look and let us know if you have any other questions! ... View more

Hello KathleenP027,   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.   Applications that integrate with Constant Contact must use the OAuth2 authorization protocol to securely authenticate a Constant Contact user account, and to be granted access to that user's data. To provide improved security, Constant Contact is now using a new authorization management service, and will be ending support for the previous service/keys on March 31, 2022.   This means that all new V3 API keys generated through the My Applications page within the Developer Portal (https://app.constantcontact.com/pages/dma/portal/) will not be compatible with applications/integrations/plugins that have not yet been updated by their developers. Additionally, if the developer does not update their application, existing API keys will no longer be able to connect to Constant Contact as of March 31, 2022.   If you have any concerns about this, please contact the application's developer directly. If the developer has any questions or concerns, you’re welcome to refer them to the article link below and/or have them follow up with us directly via email at webservices@constantcontact.com with any questions.   V3 API - Update Your Applications to Use the New Authorization Service https://v3.developer.constantcontact.com/api_guide/auth_update_apps.html   Support » Plugin: Gravity Forms Constant Contact https://wordpress.org/support/plugin/gravity-forms-constant-contact/   Please have a look and let us know if you have any other questions! ... 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.   Inquiries made to Constant Contact API Developer Support via email at webservices@constantcontact.com, or via our Developer Community, are answered in the order that they are received, and turnaround times may vary depending on volume. Typically we will be able to respond to requests within 1 to 5 business days.   Currently, if developing your own form using Constant Contact’s API, the only authentication available is OAuth 2.0 and the three flow options listed in the reply from John__B above.    If you are not wanting to go through the process of setting up OAuth 2.0 authentication to connect your website form, we also offer several pre-built form options that can be easily created and installed on your website:   Constant Contact offers a variety of pre-built hard-coded sign-up forms that are easy to create and install that will allow you to add website-signups directly from your website into your Constant Contact account:   Create a pop-up contact sign-up form for your website https://knowledgebase.constantcontact.com/articles/KnowledgeBase/21407-Create-a-Pop-up-Sign-Up-Form   Create an inline contact sign-up form to embed on a website https://knowledgebase.constantcontact.com/articles/KnowledgeBase/18265-Create-a-Sign-Up-Form-with-the-new-sign-up-form-experience   Activate and install an inline or pop-up contact sign-up form on a website https://knowledgebase.constantcontact.com/articles/KnowledgeBase/18053-activating-and-installing-your-sign-up-form   Create a Lead Generation Landing Page for capturing new sign-ups https://knowledgebase.constantcontact.com/articles/KnowledgeBase/32012-Create-a-Lead-Generation-Landing-Page-for-Capturing-New-Sign-Ups-to-Your-Contact-List   For help with settings or forms within the Constant Contact Website UI, please reach out to our Support Team at 866-289-2101. ... 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.   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 29512270.   Please have a look and let us know if you have any other questions! ... View more

Hello ChristopherM346,   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.   Applications that integrate with Constant Contact must use the OAuth2 authorization protocol to securely authenticate a Constant Contact user account, and to be granted access to that user's data. To provide improved security, Constant Contact is now using a new authorization management service, and will be ending support for the previous service/keys on March 31, 2022.   This means that all new V3 API keys generated through the My Applications page within the Developer Portal (https://app.constantcontact.com/pages/dma/portal/) will not be compatible with applications/integrations/plugins that have not yet been updated by their developers. Additionally, if the developer does not update their application, existing API keys will no longer be able to connect to Constant Contact as of March 31, 2022.   If you have any concerns about this, please contact the application's developer directly. If the developer has any questions or concerns, you’re welcome to refer them to the article link below and/or have them follow up with us directly via email at webservices@constantcontact.com with any questions.   V3 API - Update Your Applications to Use the New Authorization Service https://v3.developer.constantcontact.com/api_guide/auth_update_apps.html   Please have a look and let us know if you have any other questions! ... View more

Hello KathleenP027,   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.   Applications that integrate with Constant Contact must use the OAuth2 authorization protocol to securely authenticate a Constant Contact user account, and to be granted access to that user's data. To provide improved security, Constant Contact is now using a new authorization management service, and will be ending support for the previous service/keys on March 31, 2022.   This means that all new V3 API keys generated through the My Applications page within the Developer Portal (https://app.constantcontact.com/pages/dma/portal/) will not be compatible with applications/integrations/plugins that have not yet been updated by their developers. Additionally, if the developer does not update their application, existing API keys will no longer be able to connect to Constant Contact as of March 31, 2022.   If you have any concerns about this, please contact the application's developer directly. If the developer has any questions or concerns, you’re welcome to refer them to the article link below and/or have them follow up with us directly via email at webservices@constantcontact.com with any questions.   V3 API - Update Your Applications to Use the New Authorization Service https://v3.developer.constantcontact.com/api_guide/auth_update_apps.html   Please have a look and let us know if you have any other questions! ... View more

Hello user998024,   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.   Applications that integrate with Constant Contact must use the OAuth2 authorization protocol to securely authenticate a Constant Contact user account, and to be granted access to that user's data. To provide improved security, Constant Contact is now using a new authorization management service, and will be ending support for the previous service/keys on March 31, 2022.   This means that all new V3 API keys generated through the My Applications page within the Developer Portal (https://app.constantcontact.com/pages/dma/portal/) will not be compatible with applications/integrations/plugins that have not yet been updated by their developers. Additionally, if the developer does not update their application, existing API keys will no longer be able to connect to Constant Contact as of March 31, 2022.   If you have any concerns about this, please contact the application's developer directly. If the developer has any questions or concerns, you’re welcome to refer them to the article link below and/or have them follow up with us directly via email at webservices@constantcontact.com with any questions.   V3 API - Update Your Applications to Use the New Authorization Service https://v3.developer.constantcontact.com/api_guide/auth_update_apps.html   Please have a look and let us know if you have any other questions! ... View more

Hello user338672,   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.   What I’m seeing is the within our logs for the key generated by your account is that after the Authorization Request URL is sent and access to the account is granted, Authorization Code is being generated, but not used, and then expires.    The Authorization Code only has a lifespan of 60 seconds in which it can be exchanged for your first token set: Exchange the Authorization Code for an Access Token and Refresh Token https://v3.developer.constantcontact.com/api_guide/server_flow.html#step-3-get-the-authorization-code   Also, it looks like the key you provided in your example hasn’t been updated to use the new OAuth2 configuration that was rolled out at the beginning of this week. The instructions to do this are in the link below. You have to log into the same user that created the keys in order to edit them, as well as generate a new Secret for use in your Authorization Request:   Update Your Applications to Use the New Authorization Service https://developer.constantcontact.com/api_guide/auth_update_apps.html   This includes updating your application code to use our new authorization and token endpoints. If you do not update your application, it will no longer be able to connect to Constant Contact as of March 31, 2022.   When setting up your Authorization Request, you’ll also want to include the scope “offline_access”, which is required for returning refresh tokens in the new configuration:   OAuth2 Authorization Code Flow https://developer.constantcontact.com/api_guide/server_flow.html ... View more

Hello RondallR ,   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 our logs for your form, it looks like the key is connected and making GET calls successfully, so the error appears to be isolated to the POST calls to create new contacts. Response code 400: Bad Request indicates that either the JSON request body  was malformed or does not conform to the expected schema and that there was a data validation error.   It looks like you may have already started resolving the issue, as I do see a successful POST request today. However, if you have any follow-up questions or want us to take a look at some of the request bodies from previous failed calls, please feel free to email those logs to our team at webservices@constantcontact.com and we’d be happy to take a look. ... View more

Hello AfshinY,   Thank you for reaching out to Constant Contact API Developer Support. Inquiries made to Constant Contact API Developer Support via email at webservices@constantcontact.com, or via our Developer Community, are answered in the order that they are received, and turnaround times may vary depending on volume. Typically we will be able to respond to requests within 1 to 5 business days.   Please have a look and let us know if you have any other questions! ... 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.   The response code and example request that you provided indicate that the Access Token value being used is invalid.    V3 API Response Codes - 401: Unauthorized https://v3.developer.constantcontact.com/api_guide/glossary_responses.html#401-unauthorized   The Bearer token value in your Authorization request header must contain a valid Access Token. In order to successfully send requests, you will need to obtain an Access Token by completing authorization via OAuth 2.0 to authenticate a connection between your key/application and your Constant Contact account.   Please take a look at our OAuth2 Overview Page to select which flow will best meet your application’s needs: OAuth2 Overview https://v3.developer.constantcontact.com/api_guide/auth_overview.html#select-the-oauth2-flow-to-use   Please have a look and let us know if you have any other questions! ... View more

Hello SabrinaD460,   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'm sorry to hear that you are having list addition issues with your sign-up form. It looks like you are using the integration “Constant Contact Forms for WordPress”, which was developed by and is directly supported by Constant Contact, so I’m going to escalate this case to one of our Tier 2 support specialists so that they can follow up directly for further troubleshooting.    They should be in touch within 4 business days. Otherwise, for immediate assistance, or if you’d like a callback/email from them at a certain day/time you can call our support line at 866-289-2101 and reference case #29496120. ... View more

Hello RandyR8633,   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 29481974.   Please have a look and let us know if you have any other questions! ... View more

Hello SegmintD,   Thank you for reaching out to Constant Contact API Developer Support.    I took a look at one of the recent request bodies for one of your PUT calls to /v3/contacts/{contact_id} within our logs, which had the value for the other phone number set to blank and was not passing the properties correctly when being submitted to the API.    I did some testing, and was able to replicate what you were experiencing, that when including a value with "customFields" and "phoneNumbers" those properties are updated, (but "streetAddresses" is not).    28/Jan/2022 :00:04:20 (customer information redacted) {"customFields":[{"custom_field_id":"xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx","value":"xxxxxxxxxx"}],"phoneNumbers":[{"phone_number":"","kind":"other"}],"streetAddresses":null,"email_address":{"address":"xxxxxxxxxx","permission_to_send":"implicit","created_at":null,"updated_at":null,"opt_in_date":null,"opt_out_source":null,"opt_out_date":null,"opt_out_reason":null,"confirm_status":null},"first_name":"xxxxxxxxxx","last_name":"xxxxxxxxxx","job_title":null,"company_name":null,"birthday_month":null,"birthday_day":null,"anniversary":null,"update_source":"Account","list_memberships":["xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx","xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx","xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx","xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"],"taggings":null,"notes":null}   However, I was also able to replicate that the “other” phone number can only be overwritten with a blank value if the naming conventions of the properties in the request body match those that are specified in the Body Schema for the Contacts endpoint in our API Documentation:     "custom_fields": [     { "custom_field_id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx","value": "" }   ],   "phone_numbers": [     { "phone_number": "", "kind": "other"}   ],   "street_addresses": [     {  "kind": "home", "street": "","city": "","state": "","postal_code": "","country": "" }   ],   PUT (update) a Contact https://v3.developer.constantcontact.com/api_reference/index.html#!/Contacts/putContact   Please have a look and let us know if you have any other questions! ... View more

Hello SegmintD,   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 some of the properties in your request body may not be formatted correctly, which could be preventing those fields from mapping correctly to the corresponding contact fields.     Based on the values in the example you provided, I noticed these potential discrepancies: "customFields" should be: "custom_fields" "Custom_field_id" should be: "custom_field_id" "phoneNumbers" should be: "phone_numbers" "Phone_number" should be: "phone_number" On our API Reference page, to the right of the Tester, you can find Body Samples and Body Schemas that show how the (case sensitive) properties should be formatted for each of the endpoints that are listed:   API Reference - PUT (update) a Contact  https://v3.developer.constantcontact.com/api_reference/index.html#!/Contacts/putContact   Please have a look and let us know if you have any other questions! If you’d like us to look at any additional request body examples, you can also contact our team directly and securely via email at webservices@constantcontact.com and reference case number 29446454. ... View more

Hello user309242 ,   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 am sorry to hear that you’ve encountered difficulty with getting your account set up.   While 3rd party integrations/plugins do utilize our public facing APIs to connect with Constant Contact, they are 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 as they pertain to Constant Contact’s API endpoints and functionality.    Within our logs, I do see that you were able to generate and connect a legacy V2 API key and token with the account that you are posting from, so the integration appears to be connected successfully.   For further assistance with the functionality of the 3rd party integration/plugin, I’d recommend reaching out to the support team of the 3rd party that developed it.   Otherwise, if you are able to provide a link to the instructions you were following, the name of the integration or service you are trying to connect with, or any other relevant details, we are more than happy to see if we can assist you in locating any public-facing instructions or contact information that they might have available.   Please have a look and let us know if you have any other questions! ... View more

Hello CatR6,   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 request to develop API endpoints for other campaign types is currently under review and consideration. While we can't guarantee when or if support for campaign types other than email may be added, it currently seems most likely that any such support would be limited to reporting on published campaigns. Your feedback and experience with this request is essential to improving our product, so thank you for reaching out to us regarding this matter.   Alternatively, you might be able to find reporting data for your social media posts by looking into connecting your application with their respective APIs. However, I did some testing and took a look in Meta Business Suite, and it doesn’t look like future-scheduled Social Shares in Constant Contact appear as pending posts on the Facebook side, it looks like they are pushed through by Constant Contact at the time of deployment, so you’d probably only be able to retrieve posts that have already been published.   Twitter API Documentation https://developer.twitter.com/en/docs/twitter-api   Meta for Developers Documentation (Facebook/Instagram) https://developers.facebook.com/docs/   LinkedIn API Docs https://docs.microsoft.com/en-us/linkedin/   Please have a look and let us know if you have any other questions! ... View more

Hello AndreaL3758,   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  401 unauthorized status code indicates that you are attempting to make an API call with an expired Access Token. Access Tokens automatically expire two hours (7,200 seconds) after their last use, and have a maximum lifetime of 24 hours (86,400 seconds).   Based on the API key connected to the account that you are posting from, it looks like you're using our Client Flow, which requires you to restart the authentication process each time that your Access Token expires.    V3 API OAuth2.0 Client Flow https://v3.developer.constantcontact.com/api_guide/client_flow.html   If you would prefer that your application be able to maintain a continuous authenticated connection, you’d want to instead utilize our Server Flow, which returns both an Access Token, as well as a Refresh token that you can use to generate a new token set once the initial access token expires. Once you have your first set of tokens, you’ll want to set both the Access Token and the Refresh Token as values for corresponding variables in your application, so that when your program runs through step 5 of the OAuth2.0 Server Flow to get the new set of tokens it can assign new values to both of those variables to maintain an authenticated connection.   V3 API OAuth2.0 Server Flow https://v3.developer.constantcontact.com/api_guide/server_flow.html   You can either have the application refresh the tokens on a timer based on the life of the access token, or you can have each submission check to see if the access token is still active, and then use the refresh token to generate a new set of tokens if not.    How to Make Access Tokens Last Longer https://developer.constantcontact.com/api_guide/faqs_manage_applications.html   Please have a look and let us know if you have any other questions! ... View more

Hello AlexM760 ,   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.   Our Bulk Activity endpoints work similarly to the functionality in the UI where you can upload a file containing contacts. A successful response only indicates that the activity was created successfully and queued for processing.   Although the request may complete successfully, only active contacts are eligible to be added to lists via this endpoint. Contacts in Awaiting Confirmation status will be added to the list(s) originally specified at the time of sign-up, once they are confirmed. View a group of contacts based on their contact status https://knowledgebase.constantcontact.com/articles/KnowledgeBase/33125-View-a-Group-of-Contacts-Based-on-Their-Contact-Status   Please have a look and let us know if you have any other questions! ... View more

Hello TylerC391,   Thanks for your patience and sorry for the delayed response. Aaron had to assist an internal team with a project which took up most of his bandwidth for the week, but he did let me know that he plans to continue troubleshooting this issue with you as soon as he returns.   In the meantime, below are some third party resources that I found which may help you in narrowing down the cause of the multipart/form-data error response that you are receiving in your C# code:   [3rd party site] C# Corner - Upload Any File Using HTTP Post Multipart Form Data  https://www.c-sharpcorner.com/article/upload-any-file-using-http-post-multipart-form-data/   [3rd party site] Hot Examples - C# (CSharp) HttpMultipartParser MultipartFormDataParser Examples https://csharp.hotexamples.com/examples/HttpMultipartParser/MultipartFormDataParser/-/php-multipartformdataparser-class-examples.html   Please have a look and let us know if you have any other questions! You can also follow up with us directly via email at webservices@constantcontact.com ... View more

Hello SaraK037,   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 Power Automate / Microsoft Flow is a 3rd party product and not built or supported by Constant Contact, we are limited in the support we can provide, but will try to answer any questions to the best of our ability as they pertain to Constant Contact’s API endpoints and functionality.   From what we understand, the issue users run into regarding Power Automate / Microsoft Flow not refreshing the token set for the V3 Oauth2 Server Flow is suspected to stem from their system expecting an access token in JWT format. An error seems to occur while attempting to parse the token, which leads to the refresh failure.   I was able to find this related community post in Microsoft’s public Power Users forum that may offer some additional insight on possible resolutions (link below), but if you need further assistance with setting up an Oauth2 authentication within Power Automate / Microsoft Flow in a way that supports refreshing the token set, you’d want to reach out to their support team directly for assistance:  https://powerusers.microsoft.com/t5/Connecting-To-Data/How-to-connect-custom-API-using-own-OAuth2-in-Microsoft-Power/td-p/787697   Additionally, we have been working on some updates for our authentication system. We're still finalizing these changes, and plan to communicate the details within the next couple of weeks. I suggest keeping an eye on our documentation for those upcoming announcements: https://v3.developer.constantcontact.com/api_guide/release_notes.html   Please have a look and let us know if you have any other questions! ... View more

Hello user158539,   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 our system logs for the API key that has most recently connected with the account that you are posting from, I found quite a few responses which indicated that the authorization code might not be getting exchanged for the first Access Token and Refresh Token set within the 60 second timeframe before it expires.   When going through the V3 API OAuth Server Flow, the Authorization Code from steps 2 and 3 only has a lifespan of 60 seconds, and needs to be exchanged for your first token set within that timeframe or you will need to generate another. Until you get your first set of tokens to authenticate the connection, you will not be able to make successful calls to the API.   V3 API OAuth2.0 Server Flow https://v3.developer.constantcontact.com/api_guide/server_flow.html   If you feel that my reply was not a good fit for your inquiry, please feel free to email our team directly at webservices@constantcontact.com and provide us with the API key you are using, the username for the Constant Contact account you are connecting with, so that we can look into the issue with you further.   Please have a look and let us know if you have any other questions! ... View more

Hello user257273,   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.   In our V3 API, CORS is supported and the response should include an Access-Control-Allow-Origin header.   However, based on the logs for the API key that has recently connected with the account that you are posting from, I was seeing quite a few responses with the following error: "invalid_grant: unknown, invalid, or expired refresh token"   While the V3 API’s access tokens automatically expire two hours after their last use and have a maximum lifetime of 24 hours, refresh tokens will not expire unless they have been used and/or a new token set has been generated. However, refresh tokens can only be used once, as generating a new set of tokens causes all previous tokens (access and refresh) to expire.    Once you have your first set of tokens, you’ll want to set both the access token and the refresh token as values for corresponding variables in your application, so that when your program runs through step 5 of the OAuth2.0 Server Flow to get the new set of tokens it can assign new values to both of those variables to maintain an authenticated connection.   V3 API - Refresh the Access Token https://v3.developer.constantcontact.com/api_guide/server_flow.html#step-5-refresh-the-access-token   You can either have the application refresh the tokens on a timer based on the life of the access token, or you can have each submission check to see if the access token is still active, and then use the refresh token to generate a new set of tokens if not.    How to Make Access Tokens Last Longer https://developer.constantcontact.com/api_guide/faqs_manage_applications.html   If you feel that my reply was not a good fit for your inquiry, please feel free to email our team directly at webservices@constantcontact.com and provide us with the API key you are using, the username for the Constant Contact account you are connecting with, as well as the full request, most recent refresh token value, and the full error response that you are receiving so that we can look into the issue with you further.   Please have a look and let us know if you have any other questions!  ... View more

Hello user011501,   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 Thrive Themes uses our V2 API. I see that you were also able to successfully create a V2 key and generate a token, however, it looks like their instructions indicate that rather than generating the token yourself, you’d want to paste the key into their integration and it generates a token for you (about halfway through their instructions):   Connect your Constant Contact account through the API to your Thrive Themes products https://help.thrivethemes.com/en/articles/4647493-how-to-set-up-and-use-an-api-connection-with-constant-contact   Please have a look and let us know if you have any other questions! ... View more