Hello Warren,   Thank you for reaching out to Constant Contact API Developer Support.   Apologies, I'm not personally familiar with Microsoft Flow. However, once that initial OAuth flow is done, we return both an access and refresh token, and you can programmatically use the refresh token to get a new access token (and new refresh token) without the need for the account owner to log in and click to grant access again.   If you are getting 401 errors and reconnecting resolves it, it sounds like your refresh isn't completing successfully. Can you provide some detail on how you are refreshing your token?   Regards, David B. Tier II API Support Engineer ... View more

Hello Ravi, Thank you for reaching out to Constant Contact API Developer Support. I'm posting this here as well in case anyone comes across this post and does not see your other one. This error means that you have reached your daily call limit. Our standard API rate limit is 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) Please let me if you have any other questions! Sincerely, David B. Tier II API Support Engineer ... View more

Hello, Thank you for reaching out to Constant Contact API Developer Support. This error means that you have reached your daily call limit. Our standard API rate limit is 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) Please let me know if you have any other questions! Sincerely, David B. Tier II API Support Engineer ... View more

Hello,   Thanks for reaching out to Constant Contact's API Developer support.   There are currently no plans in place yet to deprecate the V2 API, however our V3 API will likely become preferred due to added features which are missing from V2.   Please let me know if you have any other questions!   Regards, David B. Tier II API Support Engineer ... View more

Hello Neil,   As I mentioned in my reply to your other topic, custom fields are not available through the bulk import process in our V3 API. If you are working in our older V2 API, you cannot use custom named custom fields as the V2 API can only see and use custom fields that follow a very specific naming convention (such as "Custom Field 1" for example). This is because our V2 API was designed to work with our older contacts system (which did not support custom named fields).   Please let me know if you have any other questions! Regards, David B. Tier II API Support Engineer ... View more

Hello, Thank you for reaching out to Constant Contact API Developer Support. We're still in the process of building out additional features for our V3 API, but unfortunately campaign folders are not yet available with our API. Regards, David B. Tier II API Support Engineer ... View more

Hello Neil,   Thank you for reaching out to Constant Contact API Developer Support. As of right now, custom fields are not available through the bulk import process in our V3 API, however this is a feature that our development team is actively working on. I can't say for certain when this will be available, but I am hopeful that it will come with our next major release. You can see our latest release notes as we update the API here: https://v3.developer.constantcontact.com/api_guide/release_notes.html If you are working in our older V2 API, you can currently use custom fields with some limitations. The V2 API can only see and use custom fields that follow a very specific naming convention (such as "Custom Field 1" for example) as it was designed with our older contacts system which did not have support for named custom fields. While it is possible to create custom fields with other naming formats using our website, the V2 API cannot see or interact with custom fields outside of that convention. Please let me know if you have any questions! Regards, David B. Tier II API Support Engineer ... View more

Hello,   Thank you for reaching out to Constant Contact's API Developer Support.   The exact method will depend on if you are working in our V2 for V3 API.   If you are using our V3 API you would make a PUT call to the contact as described here: https://v3.developer.constantcontact.com/api_guide/contacts_re-subscribe.html#how-to-unsubscribe-a-contact   If you are using our V2 API, the process would be as described here: https://developer.constantcontact.com/docs/contacts-api/contacts-resource.html?method=DELETE   Please have a look and let us know if you have any other questions.   Regards, David B. Tier II API Support Engineer ... View more

Hello Neil,   The access token you receive during OAuth is the Bearer token you use for making calls to the API. This access token is what tells us which Constant Contact account you are making calls to, as well as the scopes that your app has access to. You would use the Basic authentication of your API Key and Secret during the initial OAuth call, and any refresh call.   Once you have gone through the OAuth process initially, you will receive a refresh token along with your access token. The refresh token can be used to obtain a new access token (see: https://v3.developer.constantcontact.com/api_guide/server_flow.html#step-5-refresh-the-access-token) as the access token will expire after 1 hour of non-use up to a maximum of 24 hours. Depending on how often you will be making calls, you may consider building the refresh flow linked above into your application to get the new access token and refresh token before making your calls. Please have a look and let me know if you have any other questions!   Regards, David B. Tier II API Support Engineer ... View more

Hello,   Thank you for reaching out to Constant Contact API Developer Support.   Unfortunately our API does not offer webhooks. We do offer an updated subscriber email to be sent to an account owner on a daily or weekly basis. This email includes newly added contacts as well as those who have unsubscribed. For details on this email, see: https://knowledgebase.constantcontact.com/articles/KnowledgeBase/5530-automatic-email-updates-for-sign-ups-and-unsubscribes   I will make sure this feedback gets to our product management team for consideration.   Sincerely, David B. Tier II API Support Engineer ... View more

Hello,   When making calls with our V3 API, you need to include an Authorization header that includes an access token obtained through the OAuth flow. The access token is what identifies which Constant Contact account you are making calls for, and whether your application has been granted the necessary permission for the type of call you are making. Your API Key and Secret are only used in the OAuth flow, and when making subsequent calls, your API Key is identified from the access token used in your regular API calls.   The URL you would call would be: https://api.cc.email/v3/contacts?email={email_address} The headers you would use would be: Content-Type: application/json Authorization: Bearer {access_token} Please let me know if you have any other questions!   Regards, David B. Tier II API Support Engineer     ... View more

Hello,   I was able to add this character to a name field in the Constant Contact website UI, though it does not seem to be supported properly with our V3 API. I have brought this to our development team to review a possible enhancement. Please let me know if you have any other questions!   Regards, David B. Tier II API Support Engineer ... View more

Hello, Thank you for reaching out to Constant Contact API Developer Support.   There are a variety of factors involved in the sending of an automated email. Please email webservices@constantcontact.com with your Constant Contact username, and details such as: email address being added date and timeframe you added the contacts list they were added to which automated email campaign you expect to be sent to them With that information we can dig into the details on why your contacts specifically may not have been sent the automated email.   Regards, David B. Tier II API Support Engineer   ... View more

Hello,   The issue in the original post was due to a temporary system issue. I'm not aware of a repeat of that issue. Are you still having this problem? During the previous issue we were able to replicate using our API Tester page at https://v3.developer.constantcontact.com/api_reference/index.html#!/Contacts/getContacts   If you are still having the issue, do you also see it using this API Reference tester?   Please have a look and let me know if you have any questions!   Regards, David B. Tier II API Support Engineer ... View more

Hello, Thank you for reaching out to Constant Contact API Developer Support. At this time you can create an email campaign, but not yet schedule one with our V3 API. We're still in the process of building out additional features for V3. Our V2 API has the scheduling and reporting endpoints implemented and available for use; you are welcome to still develop with our V2 API. For documentation on this in V2 see the following links. Using the Email Campaign Endpoints: https://developer.constantcontact.com/docs/email-campaigns/email-campaign-api-index.html Email Campaign Schedule Collection: https://developer.constantcontact.com/docs/campaign-scheduling/campaign-schedule-collection.html?method=POST Tracking Email Campaign Results: https://developer.constantcontact.com/docs/campaign-tracking/email-campaign-tracking-.html Regards, David B. Tier II API Support Engineer ... View more

Hello, Thank you for reaching out to Constant Contact API Developer Support. Are you seeing inconsistent results for the same account, or is your integration used with multiple accounts and only some accounts return null when this call is made? Regards, David B. Tier II API Support Engineer ... View more

Hello,   Thank you for reaching out to Constant Contact API Developer Support.   We are still in the process of building out the feature set of our V3 API. As of right now there aren't any account summary endpoints that would provide you with this information, however we are hoping to have these included in our release at the end of May or beginning of June. Obviously I can't guarantee that, but that is currently what we are shooting for. Regards, David B. Tier II API Support Engineer ... View more

Hello, While there are no current plans to retire the Tags feature, our Contacts team doesn't have immediate plans for any new development involving it at this time in favor of our Segmentation feature. Our v3 API does have advanced Custom Fields features, which work well with Segments allowing you to easily segment out your list and replicate the behavior of Tags. See here for details on our Segments feature:  http://knowledgebase.constantcontact.com/articles/KnowledgeBase/25205-Define-Your-Own-List-Segments Regards, David B. Tier II API Support Engineer ... View more

Hello,   I'd like to look into this specific contact. Please email us at webservices@constantcontact.com and include the following: A code sample of how you are building this contact object The username of the Constant Contact account you are working with This way I can troubleshoot in more detail. Regards, David B. Tier II API Support Engineer ... View more

Hello,   Thank you for reaching out to Constant Contact API Developer Support.   Would you be able to verify that once you have added the address to the $contact object that it is added correctly?   Also, I'm wondering if manually setting the address might have a different outcome. E.g.: $contact->addresses[] = $address;   Regards, David B. Tier II API Support Engineer ... View more

Hello,   I know of a 3rd party plugin for Gravity Forms that can connect to constant contact. See https://wordpress.org/plugins/gravity-forms-constant-contact/ Please note that both of these are 3rd party products and not built or supported by Constant Contact directly, so I'm limited in the support I can provide with using them.   You can also create a landing page signup form within Constant Contact that will let subscribers check off which list(s) they want to sign up for. See this link for details:  https://knowledgebase.constantcontact.com/articles/KnowledgeBase/5298-edit-web-sign-up-forms   Regards, David B. Tier II API Support Engineer ... View more

Hello,   Thank you for your continued concern.   I'm asking our development team to review this further. Regards, David B. Tier II API Support Engineer ... View more

Hello,   Thank you for reaching out to Constant Contact API Developer Support.   Most of the Latin-based languages use the standard 8-bit Character Encoding that Constant Contact and virtually all email clients support. Text written in these languages can be used without any hassle or compatibility issues. Examples of 8-bit languages include English, Danish, Dutch, French, German, Italian, Norwegian, Portuguese, Spanish, and Swedish. These are also the languages that Constant Contact supports for the Email Footer/Privacy Policy.   Other languages, such as Japanese, Mandarin, Chinese, Korean, and Vietnamese use a 16-bit Character Encoding (sometimes referred to as "Double-Byte" or "Unicode" characters). Constant Contact does not officially support these languages. At this time there are no plans to change the way our API currently interacts with them in this way.   I have passed your feedback on to our product team for consideration. Please let me know if you have any other questions!   Regards,   David B. Tier II API Support Engineer ... View more

Hello,   The Access Token comes from the OAuth process and is what tells us which Constant Contact account to access, and that your app has permission to do so.   See this page in our documentation: https://v3.developer.constantcontact.com/api_guide/auth_overview.html   Regards, David B. Tier II API Support Engineer ... View more

Hello,   Thank you for reaching out to Constant Contact API Developer Support.   You will want to set your Authorization header to be "Bearer " plus whatever your access token is. So using your example:   'Authorization' => 'Bearer 0000000-0000-0000-bdde-e7d90fcf0cc7', Please let me know if you have any other questions!   Regards, David B. Tier II API Support Engineer ... View more