About John__B

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.   There isn’t a way to edit the inline and pop-up sign-up forms beyond the customization that is available in the website UI, however, you could utilize our V3 API to build your own custom sign-up form. Below I’m including documentation for our sign_up_form endpoint, which has similar functionality to that of the inline and pop-up forms offered in the website UI.   Create or Update a Contact: https://developer.constantcontact.com/api_reference/index.html#!/Contacts/createOrUpdateContact   While 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 have a look and let us know if you have any other questions!   Regards, ... View more

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

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

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

Hello SyncApps-Expert,   Thank you for your reply.   We do yet have a date set for V2 deprecation, however, it may potentially happen as soon as this year. Any future deprecation-related notices for V2 communications will likely be sent specifically to whichever email address was registered in the Mashery Developer portal  (https://constantcontact.mashery.com/) for the legacy V2 API key that the integration uses to connect.    Please let us know if you have any other questions!   Regards, ... View more

Hello DavidM0436,   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. 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, which are managed 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 current V3 API.  Your 3rd party integration may also provide you with the Redirect URI to add to your key's settings.    For a V3 API key, please follow steps 1-3 at the following link.: https://v3.developer.constantcontact.com/api_guide/apps_create.html   Otherwise, if the app you are using is asking you to also provide an "Access Token" with your API key, then it most likely utilizes our legacy V2 API, for which keys can no longer be created.   For over 3 years, we have considered creation of new V2 API Keys to be unsupported, as noted within our V2 API documentation. The Constant Contact Mashery Portal at 'constantcontact.mashery.com' has now been retired & creation of V2 API Keys is no longer possible. For any new development, please utilize our V3 API.   https://community.constantcontact.com/t5/API-Developer-Support/Creation-of-V2-API-Keys-Has-Been-Retired/td-p/427083   If you are a customer looking to use a 3rd party developed integration/form/plugin that is asking you for an API key and access token, or is asking you to generate an API key/token/secret via constantcontact.mashery.com, you will not be able to connect with this integration. Additionally, V3 keys generated within the Constant Contact Developer Portal (v3.developer.constantcontact.com) are NOT cross compatible with integrations that were built using V2, and will not work to connect with these legacy integrations.   If this is the case, please feel free to email us with the name of the  3rd party developed integration/form/plugin that you were trying to connect with, as well as links to their website/documentation, and we'd be happy to take a look and see what other comparable options may be available to look into.   If you are not the developer of the integration and have any concerns about this, please contact the integration/form/plugin's developer directly to see what their plans are, regarding updating their integration to V3. If the developer has any questions or concerns, you're welcome to have them follow up with us directly via email at webservices@constantcontact.com with any questions.  (*If you are not sure who the developer is or how to contact them, please let us know the name of the 3rd party plugin/integration/form that you are using and any additional relevant information so that we can try to provide further direction.)   If you are a developer looking to access/manage your existing keys within the Mashery Portal, you will no longer have access to the portal, though existing V2 API keys will continue to function. If any business critical changes are needed for existing V2 API keys, please email us with the API key value as well as the nature of your request, and we will see if it is something we may be able to modify from the back end of the account.   While no date is currently set, there will be a point in the near future where our legacy V2 API will begin deprecation, potentially as soon as some point this year, at which point integrations using V2 will stop working. Due to this, while we will continue to deploy critical bug fixes at this time, we will not be doing any more development for V2 or its endpoints.   If you are the developer of the integration, we strongly recommend updating the integration to use our V3 API as soon as possible, to ensure you're ahead of the curve. Our current V3 API uses OAuth2.0, which is the current industry-standard for authorization. It's more secure and does a much better job of keeping your Constant Contact account data safe. When you give their integration permission to access your account, it will show you exactly which permissions the integration is requesting to be granted (rather than just granting all permissions). V3 also uses tokens that are continuously refreshed to keep the connection encrypted and secure.   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    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!   Regards, ... View more

Hello IT-Admin,   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’ve been running into this error. If you’d like to provide us with example contacts who have run into this error when being added to your account, we would be happy to investigate and confirm the reason for the error. You can reach out to us directly with this information at webservices@constantcontact.com.   I would also mention that our engineering teams are currently working to improve the overall experience with our compliance system check when adding contacts.    Please let us know if you have any other questions!   Regards, ... View more

Hello user544507,   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 doing some research on the error you encountered, I found that this can occur as a result of an update to the cURL version that your application is using, or with an HTTP configuration issue on the server your application is running on.   While 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 have a look and let us know if you have any other questions!   Regards, ... View more

Hello AidanO03,   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 now, the only webhooks we offer are for Partners (and those are only related to billing/billing status). We don't yet offer webhooks for individual accounts' contacts, campaigns, etc.   Please let us know if you have any other questions!   Regards, ... View more

Hello TXHB,   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 have tracked your account on the open feature request for the ability to enable SSO for standard accounts.   Please let us know if you have any other questions!   Regards, ... View more

Hello JasonM15890,   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 for V3 application code samples is currently under review. However, we're currently still adding endpoints and capabilities to the V3 API, and do not plan to publish official sample apps until that process is complete. Your feedback and experience with this request is essential to improving our product, so thank you for reaching out to us regarding this matter.   For updates on which new features and endpoints have been released for Constant Contact's V3 API, you can stay updated by checking the Constant Contact V3 API Release Notes page:   V3 API - Release Notes https://developer.constantcontact.com/api_guide/index.html   In the meantime, here are the example calls that are currently available for V3:   V3 Code Samples: https://v3.developer.constantcontact.com/api_guide/tag_code_samples.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   The Client Secret is used to authorize requests made to the authorization server. You can obtain your application’s client secret in the Developer portal with the following steps:   Login to your account at https://app.constantcontact.com/pages/dma/portal/ Select the name of your V3 API key Select the blue “Generate Client Secret” button under the “App Details” section of the “Details” tab.   Please have a look and 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.   We now offer the Device authorization flow for the V3 API which is intended for applications which run on devices that are input constrained. This authorization flow does not require the use of redirect URLs, callbacks, or the client secret. I’m including our documentation on this flow below.   OAuth2 Device Flow: https://developer.constantcontact.com/api_guide/device_flow.html   Please have a look and let us know if you have any other questions!   Regards, ... View more

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

Hello HofstraContinuingEducation,   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 for V3 application code samples is currently under review. However, we're currently still adding endpoints and capabilities to the V3 API, and do not plan to publish official sample apps until that process is complete. Your feedback and experience with this request is essential to improving our product, so thank you for reaching out to us regarding this matter.   For updates on which new features and endpoints have been released for Constant Contact's V3 API, you can stay updated by checking the Constant Contact V3 API Release Notes page:   V3 API - Release Notes https://developer.constantcontact.com/api_guide/index.html   In the meantime, here are the example calls that are currently available for V3:   V3 Code Samples: https://v3.developer.constantcontact.com/api_guide/tag_code_samples.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   In order to use the V3 API endpoints, you’ll need to configure one of our available OAuth2 authorization flows. Since you mentioned the device code, I’m including our documentation for setting up the Device authorization flow below, along with overview documentation for all of our available authorization flows. Essentially, after completing the flow, you are issued an Access Token, which is sent in the authorization header of your request to the  /activities/contacts_file_import endpoint.   OAuth2 Device Flow: https://developer.constantcontact.com/api_guide/device_flow.html   OAuth2 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 JaredB71,   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 is definitely possible to schedule multiple email campaigns to multiple contact lists or segments via API. Below I’m including documentation for our V3 API’s POST (Create) an Email Campaign Activity Schedule request.   Schedule an Email Campaign Activity: https://developer.constantcontact.com/api_guide/email_campaign_create_schedule.html   POST (Create) an Email Campaign Activity Schedule: https://developer.constantcontact.com/api_reference/index.html#!/Email_Scheduling/scheduleEmailCampaignActivityUsingPOST   Please have a look and let us know if you have any other questions!   Regards, ... View more

Hello user109669,   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 sign-up form integrations, we typically recommend using the /sign_up_form endpoint, as it allows for an existing contact to have their profile updated with any new information being submitted, while the POST (create) request to the /contacts endpoint only allows for the creation of a new contact. If an existing contact’s information is submitted in a POST request to the /contacts endpoint, a 409 error is returned.   It is true that Confirm Opt-In is an account level setting that is applied to both methods. It is also expected behavior that an existing contact that has not yet confirmed their subscription can have their contact fields updated through the /sign_up_form endpoint. If Confirm Opt-In is enabled on an account, that contact can’t be sent campaigns until their subscription is confirmed.    Please have a look and let us know if you have any other questions!   Regards, ... View more

Hello DeniseB52,   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'll need some additional information in order to assist with troubleshooting. If you could please provide us with the API key that you’re using, a full example campaign scheduling request, including headers, and any timestamps or general timeframes you may have from previous failed requests, we'll be able to better assist in pinpointing the cause of the 400 error response that you’ve encountered. Please provide this information securely by reaching out to us via email at webservices@constantcontact.com, we look forward to assisting you!   Please have a look and let us know if you have any other questions!   Regards, ... View more

Hello SteveC6381,   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.   When creating a Mashery account to generate a V2 API key and Access token, your Mashery login credentials will be separate from your Constant Contact account login credentials.    Please let us know if you have any other questions!   Regards, ... View more

Hello user2865428,   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.   Thanks so much for your feedback regarding the 6MB file size limit for contact exports. It has been submitted for review and consideration by our engineering team. Your feedback and experience with this request is essential to improving our product, so thank you for reaching out to us regarding this matter.   Regarding all fields not being exported when using the Export Contacts to a File request, every contact field, including custom fields should be exported by default. When using the “fields” array, only the specified fields are exported. If you have any examples of a field not being exported when not including the “fields” array, or when including that field in the array, we would be happy to investigate if you could send an email to webservices@constantcontact.com which specifies your API key, includes a full example request, including headers, an example response, and any timestamps you may have from previous requests where this behavior occurred.   For the CSV formatting concerns that you mentioned regarding commas, one method you could use to escape the field values, which may contain commas from the commas separating the field values, is to put the field values within quotation marks.    I was able to confirm that address line 1 and address line 2 being combined in a single cell upon exporting contacts is functioning as designed, however, I would be happy to pass your feedback to the appropriate teams if you feel these fields should have their own cells.   Regarding the filtering options for the contact export request, if by GET request you’re referring to the GET Contacts Collection request, the list ID is returned in the response under the “list_memberships” property. Currently, only the list_id can be used to specify the contact list in the contact export request. I would be happy to pass your feedback regarding the ability to use the list name in place of the list_id to the appropriate team, though we can’t guarantee if or when this feature will be implemented.   GET Contacts Collection: https://developer.constantcontact.com/api_reference/index.html#!/Contacts/getContacts   Regarding segment_id’s, you can obtain all of your account’s segment_id’s by utilizing the GET all Segments request.   GET all Segments: https://developer.constantcontact.com/api_reference/index.html#!/Segments/getAccountSegments   Regarding the issue you encountered with physical address field values populating under random “Home”, “Work” and “Other” groupings in the website UI, we greatly appreciate you bringing this to our attention. I have documented this issue and passed it up to our engineering team to review for a resolution. For the meantime, the best method to ensure that these field values appear correctly under their corresponding physical address type is to group all “Home”, “Work” and “Other” address fields together in the request body as is shown in the Body sample of the JSON import request documentation I am linking below.   Import Contacts using a JSON Payload: https://developer.constantcontact.com/api_reference/index.html#!/Bulk_Activities/bulkImportContactsJSON   When you receive an error response which states “The requested resource was not found”, this typically indicates that a list, contact or segment ID used in the request was not found on the account. We would be happy to investigate this further if you could send an email to webservices@constantcontact.com which specifies your API key, includes a full example request, including headers, an example response, and any timestamps you may have from previous requests where you received this error response.   Please have a look and let us know if you have any other questions!   Regards, ... View more

Hello user62445,   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:   As with most APIs, our API has rate limits to help maintain stability and security. Our standard API access has a rate limit of 10,000 calls per day, and 4 calls per second. Once your key has hit its limit, your calls will see this error until the next day (or the next second if going over your queries-per-second limit)   429: Too Many Requests https://v3.developer.constantcontact.com/api_guide/glossary_responses.html#429-too-many-request    To avoid the queries per second error response, You could set up your application to only make synchronous refresh calls with a 1 second latency, having code execution wait for the API call to return and wait a full second before allowing another request.   If you are planning on making an application that would be available and potentially used by a large base of customers then I would suggest you look into becoming a Technology Partner with Constant Contact. There is no price involved with this and the basics are to just create and maintain your app, though there are other parts to it. Members of our partner program are given 250,000 calls per day and up to 10 calls per second. To associate your API Key with a partnership, you can look into becoming a Technology Partner: https://www.constantcontact.com/partners/technology     Also, if you'd like any insight or suggestions on cutting down on the amount of calls used based on the data that your application sends/receives, please feel free to send us an example of the endpoints you're calling and/or what specific data you need for each account and we're happy to take a look and see if we can suggest a way to use fewer endpoint calls to accomplish the same task.   Please have a look and let us know if you have any other questions!   Regards, ... View more

Hello user6365,   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 V3 API does not currently have an endpoint with the functionality that you’ve described. The 2 methods that Courtney listed above are currently the best options for obtaining contacts that have interacted with your campaigns, however, we greatly appreciate you reaching out to us with this request. It has been submitted for review and consideration by our engineering team. Your feedback and experience with this request 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 AnalyticsEdge, MarketingC731 and SyncApps-Expert,   I am pleased to inform you that the issue regarding intermittent 400 error responses from the legacy V2 API email campaign tracking endpoints has been resolved. We apologize for the inconvenience caused by this issue and greatly appreciate your patience as we worked toward its resolution.   Please let us know if you have any questions.   Regards, ... View more

Hello SyncApps-Expert,   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 we are still working to mitigate this issue and that the legacy V2 API has not yet been deprecated. I would note that while no date is currently set, there will be a point in the near future where our legacy V2 API will begin deprecation (potentially as soon as some point this year). Due to this, while we will continue to deploy critical bug fixes at this time, we will not be doing any more development for V2 or its endpoints, and strongly recommend upgrading to the V3 API to ensure you're ahead of the curve. Currently, we've already retired the V2 endpoint for Custom Code email creation, as it used an outdated version of our Custom Code editor that has been retired.   Any future deprecation-related notices for V2 communications will likely be sent specifically to whichever email address was registered in the Mashery Developer portal  (https://constantcontact.mashery.com/) for the legacy V2 API key that the integration uses to connect.   Please let us know if you have any other questions!   Regards, ... View more

Hello user87148,   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 PUT requests to the /contacts endpoint, I found that the JSON body was missing from the requests. I did some testing with the JSON request body that you provided and found that the request was successful with this format. With further testing, I was able to replicate the "update_source is missing, update_source does not have a valid value" error response that you received when completely removing the JSON body from the request.   It seems likely that some part of your workflow may not be adding the JSON body to the PUT request before it is sent.     Please have a look and let us know if you have any other questions!   Regards, ... View more

Hello AnalyticsEdge,   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 appreciate you bringing this to our attention. You are correct in that there currently isn’t a way of obtaining a Landing Page’s campaign_activity_id via the API. I have documented this issue and reported it to our engineering team who is currently in the review process for a resolution. While I am unable to provide an ETA for when this issue will be resolved at this time, we would be happy to reach out to you via email as soon as a resolution has been reached.  Your feedback and experience are 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 user6365,   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.   At this time, there is no more efficient way to get the campaign reporting data than by passing over the campaign activity id’s for the campaigns you wish to query. Enhancements to obtaining campaign reporting are under consideration for future updates, although we cannot guarantee when, or if, any specific features may be added.   One suggestion I have would be after your first full historical reporting requests to consider pulling newer campaign data daily, but pulling older data on a less frequent basis as older data is less likely to change.    Please have a look and let us know if you have any other questions!   Regards, ... View more

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