About Courtney_E

Hello kevincarbon,   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.   You should be able to fully automate your integration with the exception of the initial Authorization Request screen and redirect, which can only be accessed/authorized via a browser window and cannot be bypassed, but you should only need to authorize each connected account once.    Basically the only time you have to authorize via browser is when you initially connect the Constant Contact account, and from then on, the token set (access token and refresh token) are used to maintain the connection within your application.   For initial connection:   -Create auth request URL (make sure to include the offline_access scope) -Navigate to that URL in browser, it will have you log into the Constant Contact account you want to connect, and grant permission, which returns a code -Call the Token endpoint to exchange the code for an access token and a refresh token   If desired, you could even perform the initial authorization externally (in a program like Postman, or similar), and then just plug the access token and refresh token into your program.   Additionally, we now offer Long Lived refresh tokens, which basically ensure that the refresh token returned each time is the same value (the access token still changes), which can help prevent authorization 'breaking' in the long run due to a wrong or old value being used. I'll add more info about them at the bottom.   For maintaining the connection:   -When the access token expires after 24 hrs, a refresh token is used to make a call to the Token endpoint to return a new access token and refresh token.   A few different ways that developers maintain their token sets include:   -Refreshing the token set on a schedule -Checking to see if the access token is expired by parsing  the JWT access token for the expiration date/time, and then based on that, either continue with the endpoint call or refresh the token set -Attempting the endpoint call, and if it fails due to invalid token, then refreshing the token set and attempting the endpoint call again.  This option may be simplest, but it also uses additional endpoint calls.   About Long Lived Refresh tokens:   When using the new OAuth2 flows that are available for V3 using our recently implemented authorization management service, the access token lifetime is now a static 24 hours, and you have the option of using rotating refresh tokens or long lived refresh tokens.    Rotating refresh tokens can only be used once, and generating a new set of tokens causes all previous refresh tokens to expire, so each time you refresh the access token you will get a new refresh token value as well.   Long Lived Refresh Tokens (which can be configured within your V3 key’s settings), allow you to use the same refresh token continuously to generate new Access Tokens. You can use the same configuration as you would for the rotating refresh tokens if desired, you’ll just get back the same refresh token value each time when receiving your new access token.   Both types of refresh tokens must be used within 180 days of generation, after which they will expire. (If the long lived refresh token is used within that time frame, it will remain active and you can continue using the same value.)    While we generally recommend using rotating refresh tokens (as they're more secure), using a long lived refresh token should alleviate many of the situations that we've seen reported where a refresh token becomes invalid, and then requires a new authorization request.    -Navigate to https://app.constantcontact.com/pages/dma/portal/  -Log into the user that created the key you are wanting to edit -Open key to edit -Click "OAuth2"  tab -select "Long Lived Refresh Tokens" -Click save in upper right -You will need to authenticate and reconnect again after making this change in your key's settings   Please have a look and let us know if you or your team's developers have any other questions!   You can also reach our team directly/securely via email at webservices@constantcontact.com ... View more

Hello user443019,   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 state can be any value that you specify, and is used to prevent cross-site request forgery, specify the arbitrary state string value you want to use to uniquely identify a user’s session.   The newly added state parameter can be used to pass additional values through the Authorization Request URL. Here are three ways that you might implement this using the state parameter, from least secure to most secure:   Option 1: Use the additional value as the state value (least secure, directly exposes the additional value in the URL, and so isn't secure).   Option 2: Base64 encode the additional values, and use that as the state value (more secure, but still not random, and can be decoded).   Option 3: Come up with some formula to encode the additional values + a random value, which your program can decode when you get the response (fairly secure).   Option 4: Use a completely random state value for each additional value, save it within your application before sending the request associated with that value, then use the state value to look up the additional value upon receiving the response (most secure).   Step 1: Create an Authorization Request https://v3.developer.constantcontact.com/api_guide/server_flow.html#step-1-create-an-authorization-request   The redirect URI used when exchanging the Authorization code for a token set must match exactly both the redirect URI that was used in your Authorization Request URL, as well as the Redirect URI within your App Details for the key.   **If you are only intending to use your application for one account, you can always leave the Redirect URI as the default value and capture the code manually from the webpage URL you are redirected to after granting access.   When a user goes to connect their Constant Contact account to your integration and clicks “Allow” on the Authorization Request screen to grant your app access to their data, they are sent to the website URL that you specify as your Redirect URI. After the account owner is successfully authenticated and authorizes your application, Constant Contact redirects the account owner to your chosen redirect_uri and appends the Authorization Code to the URL, allowing your application to capture it and exchange it for your initial token set.   Get the Token from the Redirect URL https://v3.developer.constantcontact.com/api_guide/auth_overview.html#get-the-token-from-the-redirect-url    Create an Authorization Request URL https://v3.developer.constantcontact.com/api_guide/server_flow.html#step-1-create-an-authorization-request    While we don’t really have much info in our documentation regarding how to implement the Redirect URL within your application to capture the code (as our expertise is with our API itself as opposed to its implementation within any particular programming language), it should work similarly to other apps using OAuth2, and so it’s likely you’ll be able to find some applicable examples or sample code for this online.   Please have a look and let us know if you have any other questions!   You can also reach our team directly/securely via email at webservices@constantcontact.com ... View more

Hello sfogel2,   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:   To retrieve Tag IDs for your account, you'd ant to make a call to GET /contact_tags, which will return the IDs for the tags in the account.   You can either make this call via Zapier (if the connection you are using allows for it), or you can do it manually through the API Reference tester linked below and then copy the desired values over:   GET Details for All Tags https://v3.developer.constantcontact.com/api_reference/index.html#!/Contact_Tags/getTags   Please have a look and let us know if you have any other questions! ... View more

Hello user558013,   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.   You can use this flow to update your contacts which incorporates two contact endpoints:   Step 1: Get the existing contact data using the "email" query parameter to search for a contact using a specific email address.   GET Contacts Collection https://v3.developer.constantcontact.com/api_reference/index.html#!/Contacts/getContacts    Step 2: Append/modify the returned data (such as removing the physical address in question) and update the schema of the response body from the previous call so that it is correct for the request body when calling PUT /contacts.   When you update a contact using a PUT, all properties are updated, overwriting all existing property values. Any properties left blank or not included in the PUT will be overwritten with a null/blank value.   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!   You can also reach our team directly/securely via email at webservices@constantcontact.com and reference case #33082865 ... View more

Hello user6030290,   When using the "GET a Collection of Email Campaigns" endpoint, there is not a way to predetermine the amount of pages that will be returned via API. However, to cut down on required calls, you can make sure you are setting the "limit" parameter to the highest available increment of 500. If the "limit" parameter is not specified, the default amount of campaigns returned is only 50.   GET a Collection of Email Campaigns https://v3.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

Hello user6030290,   When using the "GET a Collection of Email Campaigns" endpoint, this endpoint does not allow you to query by campaign status. You would need to do this programmatically after retrieving all results.   GET a Collection of Email Campaigns https://v3.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

Hello Mary,   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 the account you are testing with may be an expired trial account. While a trial is active, it should have access to the segments tool.    More info about trial accounts here:   Constant Contact free trial https://knowledgebase.constantcontact.com/articles/KnowledgeBase/5549-constant-contact-free-trial   In order to test with segments via the API without creating a paid account or upgrading your existing trial account, you can just create a new trial account (which will be "active" for 30 days) using a different email address.   Please have a look and let us know if you have any other questions!   You can also reach our team directly/securely via email at webservices@constantcontact.com and reference case #33015905. ... View more

Hello user416572,   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 sounds like you may be trying to execute the OAuth2 authorization behind the scenes, as I am not seing any authorization requests within our logs for your key.The Authorization Request screen can only be accessed/authorized via a browser window or a pop up browser dialog, but you should only need to authorize/connect each account once via this method.   If you continue to run into issues, please reach our team directly/securely via email at webservices@constantcontact.com and reference case #32983566 and provide us with the full request(s) where you are receiving the response (including URL, headers, timestamp, and request body), and the full response body so that we can better assist you in identifying the root cause of the issue.   Please have a look and let us know if you have any other questions! ... View more

Hello EdR,   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 have followed up with you via email (the address on file for the account that you are posting from) regarding the issue that you are running into. If you have not received this email, please feel free to email us directly from the address of your preference at webservices@constantcontact.com and reference case #32966038.   Please have a look and let us know if you have any other questions! ... View more

Hello user61100,   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.   Typically when unauthorized is returned, it can mean that the permissions granted were revoked, or that the account user (usually an account manager) that initially connected the integration has been disabled or removed by the account owner, or that the account manager's role was changed to a campaign creator and no longer has the needed authorization for the required permissions .    If a user that created an API key is deleted, the API key remains active and will continue to work. However, depending on the key type, you may not be able to access or make changes to that key via the other users on the account.   If you're still running into this issue, please feel free to reach out to our team directly/securely via email at webservices@constantcontact.com with the API key in question, referencing case #32618346, and we'd be happy to take a look and see if we can determine the cause of the error.   Please have a look and let us know if you have any other questions! ... View more

Hello EdR,   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.   Please feel free to email us directly at webservices@constantcontact.com and reference case #32931560 requesting additional assistance regarding the OAuth2 Authorization Code Flow in Postman.   Please have a look and let us know if you have any other questions! ... View more

Hello EdR,   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.   Please feel free to email us directly at webservices@constantcontact.com and reference case #32931560 requesting additional assistance regarding the OAuth2 Authorization Code Flow in Postman.   Please have a look and let us know if you have any other questions! ... View more

Hello Beby,   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 don't have dedicated developer/sandbox accounts per se, but you are able to create a free developer trial account with limited sending capabilities which you can use for your testing purposes. Trial accounts created through the developer portal do not expire, whereas standard trial accounts created through the main site expire after 60 days if not converted to a paid account. Below is a link to our developer portal where you can sign up for a trial account, you'll just need to click on "Get Started" and then "Sign up".   Constant Contact Developer Portal https://developer.constantcontact.com/    Please have a look and let us know if you have any other questions! ... View more

Hello RamonL49,   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 provides developers with free access to our V3 API endpoints for developers building their own application for integration. You can get started using our API by visiting our documentation here: https://v3.developer.constantcontact.com/api_guide/getting_started.html    Our developer portal uses the same credentials and login session as your Constant Contact account. As a side note though, V3 API keys generated via the Developer Portal are not universal to the account and can only be accessed by the logged in user that created them.   Additionally, you can utilize our API Reference Page to find body schemas & values, as well as test the functionality of our available endpoints to see how they will work once programmed within your application: https://v3.developer.constantcontact.com/api_reference/index.html    While Constant Contact's API Developer Support team doesn’t offer any services as far as assistance with building custom integrations, and our expertise is with our API itself as opposed to its implementation within any particular programming language, we are happy to answer any questions pertaining to Constant Contact’s API endpoints, functionality, and documentation.   Please let us know if you have any questions about getting started with Constant Contact's API! ... View more

Hello ChristopherGronbeck,   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.   Thank you for bringing that to our attention, as the page that you referenced is now out of date. I'll be submitting a ticket to get that resolved.   Instead, please feel free to reference this page, as it has up to date information on the V3 API's OAuth processes: https://developer.constantcontact.com/api_guide/auth_overview.html   When using the new OAuth2 flows that are available for V3, the access token lifetime is a static 24 hours, and you have the option of using rotating refresh tokens or long lived refresh tokens.    In regards to scheduling, you could refresh the access/refresh tokens daily, or you could have your program check to see whether the current access token is still valid, and if not send a new token request.   The access token is a JWT token, so you can parse the JWT access token for the expiration date/time and/or granted scopes. You can either look for a standalone JWT decoder tool or set up a decoder within your program’s code so that it can programmatically verify the remaining lifetime of the access token before attempting to refresh.   Regarding Long Lived Refresh Tokens (which can be configured within your V3 key’s settings), these allow you to use the same refresh token continuously to generate new Access Tokens. You can use the same configuration as you would for the rotating refresh tokens if desired, you’ll just get back the same refresh token value each time when receiving your new access token.While we generally recommend using rotating refresh tokens (as they're more secure), using a long lived refresh token should alleviate many of the situations that we've seen reported where a refresh token becomes invalid, and then requires a new authorization request.    Please have a look and let us know if you have any other questions!   You can also reach our team directly/securely via email at webservices@constantcontact.com ... View more

Hello Lacey,   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.   You should be able to fully automate your integration with the exception of the initial Authorization Request screen and redirect, which can only be accessed/authorized via a browser window and cannot be bypassed, but you should only need to authorize your connected account once.   The Authorization Request screen is only for connecting a Constant Contact account to the integration, so for example if you are making a sign-up form or integration that only connects to one Constant Contact account, only you would access the Authorization Request screen one initial time to connect your account, it wouldn't be visible to people using the form/integration.  When your users are accessing the integration, it will use the token set generated when you initially granted permission to access the connection. The only time other people would access the Authorization Request screen is if you are designing an integration that needs to connect to other Constant Contact accounts, as each account needs to grant permission to the integration.   For more detailed steps on getting started with the authorization process, feel free to email us at webservices@constantcontact.com and reference case #32748247   Please have a look and let us know if you have any other questions! ... View more

Hello Fiodor,   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.   Once you have the encoded_account_id for a child account, you can then send API requests on behalf of a managed client account. This includes all of the endpoint calls that are available to standard accounts, but they need to be reformatted to fit the request body schemas for the partner endpoint.   Send API Requests on Behalf of Managed Client Accounts https://v3.developer.constantcontact.com/api_guide/partners_master_token.html   Below is an example of the same call to GET /contacts with a specific email address with the partner endpoint vs. the corresponding standard endpoint:   Standard request URL and body:   GET  V3/contacts?status=all&email=dlang@example.com&include=custom_fields,list_memberships,phone_numbers,street_addresses,taggings,notes   Request Body: {none}   Partner request URL and body:   POST  V3/partner/accounts/{encoded_account_id}/account_operations/sync   Request Body: { "account_operation_url": "/contacts", "account_operation_method": "GET", "account_operation_query_parameters": [ {"query_param_key": "email", "query_param_value": "dlang@example.com"}, {"query_param_key": "status", "query_param_value": "all"}, {"query_param_key": "include", "query_param_value":"custom_fields,list_memberships,phone_numbers,street_addresses,taggings,notes"} ], "account_operation_headers": [ { "header_key": "Accept", "header_value": "application/json" } ] }   Please have a look and let us know if you have any other questions! ... View more

Hello EdR,   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.   There are several significant differences between our V2 and V3 APIs, including the use of different endpoints, OAuth 2.0 rather than basic authentication, JSON payloads instead of XML, and a different format for resource identifiers.   A quick start guide for the V3 API can be found here: https://developer.constantcontact.com/api_guide/getting_started.html    While the rest of our documentation is linked from the quick start guide, the following pages in particular may be useful: https://developer.constantcontact.com/api_guide/v3_technical_overview.html  https://developer.constantcontact.com/api_guide/developer_portal.html  https://developer.constantcontact.com/api_guide/migration_overview.html    Additionally, you can utilize our API Reference tester to test out the functionality of our available endpoints to see how they will work once programmed within your application: https://v3.developer.constantcontact.com/api_reference/index.html    [Step 1:] Get the "campaign_id" of the campaign(s) that you want the URL for. When you GET campaigns, it will return all campaigns. Sent campaigns will be those that show "current_status": "Done":   GET a Collection of Email Campaigns https://v3.developer.constantcontact.com/api_reference/index.html#!/Email_Campaigns/retrieveEmailCampaignsUsingGET    REQUEST URL https://api.cc.email/v3/emails   RESPONSE BODY "campaign_id": "8987dc1a-48ef-433a-b836-7ca4f9aa3481"   [Step 2:] Use the "campaign_id" to get the "campaign_activity_id" for "role": "primary_email":   GET Details About a Single Email Campaign  https://v3.developer.constantcontact.com/api_reference/index.html#!/Email_Campaigns/retrieveEmailCampaignUsingGET    REQUEST URL https://api.cc.email/v3/emails/8987dc1a-48ef-433a-b836-7ca4f9aa3481   RESPONSE BODY "campaign_activity_id": "0e3feddd-c8da-4d53-a507-aae5082b8b75", "role": "primary_email"   [Step 3:] Use the "campaign_activity_id" to call the corresponding Email Reporting endpoints that you would like info for:   GET an Email Links Report https://v3.developer.constantcontact.com/api_reference/index.html#!/Email_Reporting/getCampaignActivityLinkStats   GET an Email Sends Report https://v3.developer.constantcontact.com/api_reference/index.html#!/Email_Reporting/getSends   GET an Email Opens Report https://v3.developer.constantcontact.com/api_reference/index.html#!/Email_Reporting/getOpens   GET an Email Clicks Report https://v3.developer.constantcontact.com/api_reference/index.html#!/Email_Reporting/getClicks   GET an Email Opt-outs Report https://v3.developer.constantcontact.com/api_reference/index.html#!/Email_Reporting/getOptouts   GET an Email Bounces Report https://v3.developer.constantcontact.com/api_reference/index.html#!/Email_Reporting/getBounces   If you would like us to send you additional information regarding getting started with V3 authorization and/or endpoints, or have any further questions, please feel free to reply directly to this email so that we can assist further.   Please have a look and let us know if you have any other questions! ... View more

Hello ColinHuronCoC,   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 was able to find an open ticket for this issue, and it looks like a fix was pushed out on 7/14/24.    The ticket also notes that if you are still experiencing the issue, that it is likely due to stored cache/cookies from prior to the fix, and that clearing the cache/cookies for the time range of "all time" should fix the issue.   If you have further questions regarding this issue, please reach out to Constant Contact's Support Team at 866-289-2101 and reference case #32626962.   Please have a look and let us know if you have any other questions!   ... View more

Hello AmandaL921,   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, it looks like you may have already resolved this issue, however, this is what I found:   It looks like the address in question was being added to the campaigns via the JSON request body of PUT calls that were being made to /emails/activities/{campaign_activity_id}, within the physical_address_in_footer parameter.   Please have a look and let us know if you have any other questions! ... View more

Hello user84168,   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.   Could you please email our team with the API key that you are using to make the request, the full request(s) where you are receiving the response (including URL, headers, timestamp, and request body), and the full response body so that we can better assist you in identifying the root cause of the issue?   You can reach our team directly/securely via email at webservices@constantcontact.com   Please have a look and let us know if you have any other questions! ... View more

Hello Janehelm1014,   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 sounds like the form was set up and connected successfully if you are able to view the lists. Please feel free to email us some examples of addresses that were used in the form but not added and we'd be happy to look into them for you to see what might be causing the issue.   You can reach our team directly/securely via email at webservices@constantcontact.com   Please have a look and let us know if you have any other questions! ... View more

Hello TomP1,   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.   For a PUT call to /contacts, the contact ID should go in the request URL, rather than the request body.    You can check the request URL details and body schema in our API Tester at the link below. In the upper right where it says "BODY SAMPLE" you can expand the section to see an example of how the JSON request body should be formatted.   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 continue to run into issues, feel free to reach our team directly/securely via email at webservices@constantcontact.com with your full request URL and JSON request body, referencing case #32589373. ... View more

Hello KorashH,   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 you are missing the bracket after  "email_campaign_activities" and also the "physical_address_in_footer" section from your JSON request body.    Example: {     "name": "value",     "email_campaign_activities": [         {             "format_type": 5,             "from_name": "value",             "from_email": "value@value.com",             "reply_to_email": "value@value.com",             "subject": "value",             "html_content": "<html><body>value<\/body><\/html>",             "physical_address_in_footer": {                 "address_line1": "value",                 "address_line2": "value",                 "address_line3": "value",                 "address_optional": "value",                 "city": "value",                 "country_code": "value",                 "country_name": "value",                 "organization_name": "value",                 "postal_code": "value",                 "state_code": "value",                 "state_name": "value",                 "state_non_us_name": "value"             }         }     ] }   Create an Email Campaign https://v3.developer.constantcontact.com/api_guide/email_campaign_create.html   Please have a look and let us know if you have any other questions! ... View more

Hello BradH350,    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 sounds like you may be trying to use a 3rd-party app that is asking you for an API Key with a specific Redirect URI. Usually an application developer will generate their own API Key that lets their app integrate with Constant Contact, however some developers require you to provide them with an API Key. Since this process was designed to be done by the app developers themselves, it can be confusing for end users to find or generate this information.   We have two different versions of our API, so the steps you take to generate an API key will depend on what version of our API the integration you are looking to connect with uses, as they are created through different platforms and are not cross compatible.   If the app you are using is asking you for an API Key and Secret, then it most likely utilizes our V3 API.  Your 3rd party integration may also provide you with the Redirect URI to add to your key. Follow steps 1-3 at the following link.: https://v3.developer.constantcontact.com/api_guide/apps_create.html   If you are still running into issues, or the steps don't match the instructions that you are following, please send us a link to or copy of the instructions that you were provided so that we can try to provide additional insight.    You can reach our team directly/securely via email at webservices@constantcontact.com   Please have a look and let us know if you have any other questions!   ... View more