Hello Samuel,   My name is Caleb and I am a member of Constant Contact's API Developer Support Team.   In order to retrieve the campaign_activity_id for a given campaign you will first need to retrieve the campaign_id for the campaign. If you are unfamiliar with how to find this then you will want to first make GET request to the endpoint '/emails' which will retrieve the collection of email campaigns from your account. The response you receive from this request will provide you the campaign_id unique to each campaign which will be needed in order to make the next request.   GET a Collection of Email Campaigns: https://developer.constantcontact.com/api_reference/index.html#!/Email_Campaigns/retrieveEmailCampaignsUsingGET   Once you have retrieved the campaign_id for the campaign you will then want to make a new GET request to the endpoint '/emails/{campaign_id}'. This request will return all of the campaign_activity_id's for the specified campaign (minimum of two activity ids). The default activity id's have a role of either 'primary email' or 'permalink' (it is possible that you may have more activity ids if the campaign has been resent to non openers). Out of these activity_ids you will only need the activity_id with a role of 'primary email'.   GET Details About a Single Email Campaign: https://developer.constantcontact.com/api_reference/index.html#!/Email_Campaigns/retrieveEmailCampaignUsingGET   After retrieving the correct campaign_activity_id with a role of 'primary email' you will then be prepared to make a request to the endpoint '/emails/activities/{campaign_activity_id}/tests' which will then allow you to send a test email to the associated email_address in the body of the request.   POST Test Send an Email Campaign Activity: https://v3.developer.constantcontact.com/api_reference/index.html#!/Email_Scheduling/testSendCampaignActivityUsingPOST ... View more

Hello Dalena,    My name is Caleb and I am a member of Constant Contact's API Developer Support.    We are happy to see that you were able to verify the cause of this issue. If you have any questions regarding the use of our API please be sure to either reply to this forum post or if the matter contains more private information feel free to send us an email at 'webservices@constantcontact.com' with as much detail pertaining to the issue as available and we will be more than happy to assist you! ... View more

Hello,   My name is Caleb and I am a member of Constant Contact's API Developer Support Team.   Due to the design of our automated series only being capable of creating GUI campaigns paired with our API only being capable of creating custom coded campaigns prevents us from being capable of opening an endpoint for the creation of automated series through the API. That being said, you are able to trigger a pre-existing list-join automated series by adding contacts through the API into the associated mailing list for the series. This does require that you set the series up within the account, however it is the only method that will allow for the API to interact with the series.   Create an Automated Series: https://knowledgebase.constantcontact.com/articles/KnowledgeBase/27935-Choosing-a-Trigger-for-Your-Automated-Email-Series ... View more

Hello CaframoAdmin,    My name is Caleb and I am a member of Constant Contact's API Developer Support Team.    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 29092410. ... View more

Hello,   My name is Caleb and I am a member of Constant Contact's API Support Team.   After reviewing the request provided I have been able to identify the cause of this issue as having a missing underscore for 'phone_numbers": ['. This allowed for the system to successfully create the contact record (201 success) however it prevented the creation of the phone number field as there was no matching label due to the missing underscore. I am able to confirm that once correcting the request to include the underscore that this now creates the contact correctly and shouldn't pose any further issues. ... View more

Hello,   My name is Caleb and I am a member of Constant Contact's API Developer Support Team.   The difference between the sources is dependent on who is taking the action to add or update the contacts. For example, if a contact were to use a sign up form you would want the source to be 'Contact'. Whereas if the account owner were to be the one utilizing the integration to pull in an existing mailing list you would want the source to be 'Account'.   Please note that only the create_source = 'Contact' is able to trigger the welcome email. Only use this method when a contact gives you their explicit permission to send them emails. It is a violation of US and Canadian anti-spam laws, as well as a serious violation of the Constant Contact Terms of Service to use the Opt-in features of the API to opt a contact back in without his or her own action and consent.   Contacts Overview V3 API: https://developer.constantcontact.com/api_guide/contacts_overview.html ... View more

Hello Mageshwarri,   My name is Caleb and I am a member of Constant Contact's API Developer Support Team.   The error message that you are receiving is typically caused by an invalid refresh token. Our refresh tokens do not have a set expiration time and instead the only way for a refresh token to become invalid would be for either the token to be used to refresh the access token or for a new authorization request to be made using the same API Key and the same Constant Contact user account. That being said, there are a few common situations which other users have experienced that may be the reason you are experiencing this error message.   The first common situation would be that your application is not storing the new refresh tokens after using the initial refresh token. This is due to the refresh token becoming invalidated after a successful refresh request as a new refresh token will be generated. To prevent this specific circumstance you will want to verify that your application is updating the refresh token variable to the new value after a successful refresh request.   The second most common situation would be if you have multiple instances of your application running on more than one machine without a shared database. This is caused by having one instance of the application successfully send a refresh request resulting in a new refresh token being generated. Without a shared database for your application to reference the newly generated token will invalidate the original refresh token resulting in the other instance of the application being no longer able to refresh its tokens as the initial refresh token was used in the other instance.   The final most common situation would be if your application is making non-blocking (asynchronous) refresh attempts when receiving the 401 response to another API request. This can result in your application sending multiple refresh attempts without first verifying that a response (with a new access and refresh token) has been received. This causes any requests made after the initial request to be invalidated resulting in the invalid error message. To prevent this, your application would need to send the refresh request upon receiving the 401 response and then wait for a response from the API before proceeding with further API calls.   If these situations do not align with how your application is behaving then we will need to have you log the requests, responses, the timestamps, as well as any error messages you are receiving and send these logs to us by email 'webservices@constantcontact.com'. This will allow us to evaluate the behavior and properly identify the cause of the invalid refresh token. ... View more

Hello Kevin,   My name is Caleb and I am a member of Constant Contact's API Developer Support Team.   When using the authorization URL a user will always be prompted to login to the account they would like to grant the application access to unless that user is currently logged into a Constant Contact account that has previously authorized the application. Typically this action only occurs when first using a new integration as once they have provided permission for the application to make changes to the account the application will have an access token to make calls with.   In your circumstance, you are attempting to re-authorize the application on your new system which did not have a Constant Contact account logged in, this prompted the request to login to the account and authorize the application again. Once the user has authorized the application on their machine you should be able to prevent them from needing to re-login by keeping the tokens refreshed.   Additionally, if you are connecting to Constant Contact as the same user on both systems without sharing your token information you will find that the two instances of the application will invalidate the other's tokens. To prevent this issue there will be a couple of different solutions. The optimal solution to this issue would be to share the token information over a shared server which would allow the application to always stay authenticated and would prevent the need for the users to login when signing in on a new machine. If this option is not available you will then want to either have each instance of the application use a new API key or you will want to sign into the Constant Contact account using a different users login information for each instance as the access token is unique to the user which signed in.   Moving forward, once the application has been authorized you will then want to have your application keep itself authorized with the account by utilizing the the refresh token found in step 5 of the OAuth 2.0 Server Flow. Below I have linked to the documentation which covers this as well as a link to how to keep these tokens active.   OAuth 2.0 Server Flow: https://developer.constantcontact.com/api_guide/server_flow.html   Extending the Life of Tokens: https://developer.constantcontact.com/api_guide/faqs_manage_applications.html ... View more

Hello,   My name is Caleb and I am a member of Constant Contact's API Developer Support Team.   Based on the description it sounds like you are utilizing our WordPress Sign Up Form Plugin and are finding that the contacts are not being added from the form into your account. This form by default is configured to have a slight delay when a contact signs up before passing the information over to your Constant Contact account, however we have found that this delay can occasionally prevent a contact from being added.   By reviewing our database logs I was able to find the example contact 'paolabianca.mangubat@gmail.com' which was added using this sign up form. It appears that while the contact had used the form on September 12th that they were not added into the account until September 13th at 5:04 am. This delay was caused by the form itself, however there is a setting within the form that can be used to send the contact's information over more quickly. To do this you will want to do the following:   - Navigate into your WordPress Dashboard. - Select the Contact Form Plugin. - Navigate to the settings of the plugin - Check the box next to 'Bypass Constant Contact Cron Scheduling' - Save the changes at the bottom   Once this setting has been enabled you should find that your contacts are being sent over more immediately. If for any reason this change does not resolve the issue or in case you have further questions regarding this we have gone ahead and escalated this issue to our specialists which will be following up with you via the email on file with your account.  ... View more

Hello Oscar,   My name is Caleb and I am a member of Constant Contact's API Developer Support Team.   The error message that you are receiving appears to be a 404 error message which is caused when one of the requested 'campaign_ids' are invalid. In order for a 'campaign_id' to be valid, the campaign must have been sent prior to making the request as campaigns in the draft status will result in a 404 error message.   Another possibility is that the request you are using is miss-formatted which can also result in the system returning a 404 error message. Please be sure that your request is formatted with the {campaign_id} portion of the request URL being replaced with the appropriate campaign_ids you are requesting. For example your request should be formatted as:   - https://api.cc.email/v3/reports/stats/email_campaigns/1e63bc73-74c1-4046-bcb4-e8b1173b8af4   If you are still receiving an error message when making this request please be sure to send us an email at 'webservices@constantcontact.com' with the request, the response, the error message, any timestamps available, as well as any other information you believe may be useful in helping troubleshoot this issue. ... View more

Hello Andrew,   My name is Caleb and I am a member of Constant Contact's API Developer Support.   After a review of your account I have been able to identify an API key which has recently been utilized, however I was not able to identify specific requests which resulted in an error response. Due to this, could you please email us directly at 'webservices@constantcontact.com' with your API key, the full error response, timestamps of the example error messages, as well as the request that is being used to call the server in order to better assist you. ... View more

Hello,   My name is Caleb and I am a member of Constant Contact's API Developer Support.   Upon reviewing your account it appears that you are already making use of our non-expiring trial accounts which are meant for developers to use as a testing environment. I have also found that your account has only sent to 10 out of the total allowance of 100 contacts. Based on this, your account should still be capable of scheduling campaigns and does not require any type of an upgrade.   Are you receiving any type of an error message when attempting to schedule campaigns through the API or are you attempting to schedule these through the user interface directly? If you are receiving an error message while attempting to schedule through the API then please be sure to follow up with us by sending an email to 'webservices@constantcontact.com' with any example payloads as well as any example error messages that you are receiving. If you are receiving the error message while scheduling through the site itself then please refer to our support team at 866-289-2101. ... View more

Thank you for reaching out to Constant Contact API Developer Support, my name is Caleb. My team is here to assist outside software developers with questions about building into Constant Contact's API.   The error message 'Invalid email address' is typically caused by our compliance system detecting multiple sign ups to several Constant Contact accounts from the email address that caused the error. I can confirm that all 5 of the listed examples have been detected as having signed up to multiple accounts in a short time causing the system to block sign ups from these addresses.   If you have further questions about these error messages please feel free to reach out to our Account Review department and they would be happy to answer any concerns you may have.   Contact an Account Review Specialist: https://knowledgebase.constantcontact.com/articles/KnowledgeBase/5782-contact-an-account-review-and-deliverability-specialist   ... View more

It looks like we reached out to you via email regarding this issue to request some additional information in order to better assist with troubleshooting. If you still need assistance with this, please let us know! If you haven't received our reply, please let us know via email at webservices@constantcontact.com, and reference case number 28618073. ... View more

Thank you for reaching out to Constant Contact API Developer Support, my name is Caleb. My team is here to assist outside software developers with questions about building into Constant Contact's API.   We do support the use of the state parameter, however with the parameter not being passed through successfully we believe that the value that is being used may be the source of the issue.   To further test this issue we'll need some additional information. If you could please provide us with examples of the request using the state parameter we'll be able to better assist in pinpointing the cause of the parameter not being passed through. Please provide this information securely by reaching out to us via email at webservices@constantcontact.com, we look forward to assisting you! ... View more

Thank you for reaching out to Constant Contact API Developer Support, my name is Caleb. My team is here to assist outside software developers with questions about building into Constant Contact's API.   We do currently have a plugin that would allow you to syncronize your contacts from Magento to your Constant Contact account, however this plugin requires that you use a newer version of Magento which is version 2.4.1 or above.   Connecting Your Magento Store: https://knowledgebase.constantcontact.com/articles/KnowledgeBase/41006-Connect-Your-Constant-Contact-Account-with-Magento   If you are unable to update your Magento store to a newer version an alternative method would be to develop a plugin yourself using both Magento's APIs as well as our own.   Magento API Starting Guide: https://devdocs.magento.com/guides/v2.4/get-started/bk-get-started-api.html   Constant Contact API Quick Start Guide: https://developer.constantcontact.com/api_guide/getting_started.html   The final option would be to search for an existing third-party plugin that would connect your store to your Constant Contact account that meets your current store's version. ... View more

My name is Caleb and I'm a member of Constant Contact’s API Developer Support.   The V3 API does not have the ability to sort contacts / campaigns directly, however we are able to create a request which would provide a response that you can then use to parse and sort the data for the 'created_at' and 'updated_at' times you need.   To help gather more relevant data we are able to filter both contacts and campaigns based on the 'updated_at' value that the contact / campaigns currently have. For contacts this can be achieved by setting your parameter as 'updated_after' and setting the value as the appropriate updated_at time (ISO-8601 Format) to get more relevant responses. There are further examples of how to do this as well as other criteria that you can use in the link provided below.   Get a Collection of Contacts: https://developer.constantcontact.com/api_reference/index.html#!/Contacts/getContacts   An alternative method to filtering by the updated_at values for contacts would be to make a request to create a .csv file which would contain both values which you can then parse the response for the data.   Exporting a CSV File: https://developer.constantcontact.com/api_reference/index.html#!/Bulk_Activities/postContactsExport   For campaigns you will need to set the parameter as either 'before_date' or 'after_date' and set the value to the appropriate updated_at time (ISO-8601 Format) to gather more relevant responses. You may also use these parameters to get a range of campaigns last updated within a specific time-frame. I have provided the link which explains this process in further detail below.   Get a Collection of Emails: https://developer.constantcontact.com/api_reference/index.html#!/Email_Campaigns/retrieveEmailCampaignsUsingGET   Please have a look and let us know if you have any other questions! ... View more