Hello,   We use current OAuth standards for security purposes. Access tokens are good for up to 24 hours. Refresh tokens don't expire, but will become invalid if they are used or if the initial authorization flow is completed again. If you could use the same refresh token over and over, that kind of defeats the purpose of having a rotating access token.   When you use your refresh token, you get a new access token and a new refresh token as well. You then use the new access token until it expires, and refresh using the refresh token that was given at the same time as the access token you were just using.   Typically in a situation such as yours where you have multiple users making calls for the same Constant Contact account, you would have your server control all of your calls, storing the access and refresh token, and refreshing it when needed. Please let me know if you have any other questions.   Sincerely, David B. Tier II API Support Engineer     ... View more

Hello,   What scope are you using in your OAuth authorization flow? Regards, David B. Tier II API Support Engineer ... View more

Hello,   Our inline form that is available within your account is not able to have a placeholder and instead has a label above the field. You may find using our Constant Contact Forms for Wordpress plugin more to your liking as this does let you set placeholder text. For more details about it see: https://knowledgebase.constantcontact.com/articles/KnowledgeBase/Using-Constant-Contact-Forms-for-WordPress-Video?lang=en_US   Regards, David B. Tier II API Support Engineer ... View more

Hello,   Thank you for that information. It looks like you are building your authorization header to have braces { } around your access token. These are not needed, so you should build your header like this: curl_setopt($ch, CURLOPT_HTTPHEADER, array('authorization'=>'Bearer '.$access_token)); Please give that a try and let us know how that works.   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 can only be called from the back end of a website. There are no current plans to add support for cross-origin resource sharing, so you would need to use a server-side process to make the actual calls to our API.   Solutions that others have used is to have a separate server and pass data via AJAX to that separate server, which then makes the API calls on your server behind the scenes.   Please let me know if you have any questions!   Regards, David B. Tier II API Support Engineer ... View more

Hello,   The back slashes are only needed when breaking up the request into multiple lines. Since you are doing this all on one line, they can be omitted. For example:   curl -X POST https://api.cc.email/v3/activities/contact_exports -H 'Accept: text/csv' -H 'Content-Type: application/json' -H 'Authorization: Bearer {access_token}' -H 'Cache-Control: no-cache' -d '{ "list_ids": [ "f5cb02a0-88c7-11e5-9497-d4ae5275b546" ], "fields": ["email_address"], "status": "active" }' Please give this a try and let me know if that works for you.   Sincerely, David B. Tier II API Support Engineer     ... View more

Hello Eryn,   Thank you for reaching out to Constant Contact API Developer Support. It sounds like you are trying to use a 3rd-party app that is asking you for an API Key and/or an access token. It is most common to use our older V2 API for this.   Usually an application developer will generate their own API Key that lets their app communicate with Constant Contact, however some developers require you to provide them with your own API Key and/or Access Token. Since this process was designed for developers, it can be confusing for non-developers to find or generate this information. To help de-mystify the process for everyone, we have a blog post which walks through step-by-step instructions on how to get that information.   How to generate an API Key and Access Token: https://community.constantcontact.com/t5/Community-News/How-to-generate-an-API-Key-and-Access-Token/ba-p/293856   If the app you are using does not give you a redirect URI in their documentation (and is only asking for an API Key and Access Token for example), you can just use the default value of: http://localhost   Please have a look and let us know 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.   The likely cause of your issue is that you are going over your calls per second rate limit. Our standard API access limit is 10,000 calls per day and 4 calls per second. If you make more than 4 calls per second, any additional calls will return with a 401 error until after 1 second after the first call was attempted.   Please let me know if you have any other questions!   Regards, David B. Tier II API Support Engineer ... View more

Hello Sherry, Thank you for reaching out to Constant Contact API Developer Support. Depending on how Dealcloud's API works it may be possible for an integration to be built between them and Constant Contact. There is no additional charge from us for using our API, however an integration like this would not be something built by Constant Contact and would need to be built by either Dealcloud or a 3rd party. If you are looking for a developer who is familiar with our API to build something completely custom for you, you may find someone to work with in our marketplace here: http://marketplace.constantcontact.com/ServicesSearch?sort=rating&query=&need=Software+Development 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. I'm sorry, at this time we don't have a method of searching for contacts by their created date. You can only search for contacts using the following criteria: - Contact status - Email address - updated_after - list membership Unfortunately in order to see newly created contacts you would still need to parse through contacts to find new ones, however you can avoid having to get all contacts by using updated_after of your specific timeframe which will limit the contacts you need to loop through. I will bring this to our development team's attention as a possible feature enhancement on your behalf. 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 API Developer Support. A contact is never truly deleted from within a Constant Contact account, it's simply removed from all lists and no longer visible in the account.   The reason we do this is to maintain data such as accurate reporting, and unsubscribe status behind the scenes. This is also why you cannot POST a new contact with the same email address as a removed/deleted contact; you would need to update the existing "deleted" contact instead.    See our PUT documentation here:  https://v3.developer.constantcontact.com/api_reference/index.html#!/Contacts/putContact Please have a look and let me know if you have any other questions!   Sincerely, David B. Tier II API Support Engineer ... View more

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