About David_B.

David_B. · ‎10-31-2019

Hello, Thank you for reaching out to Constant Contact API Developer Support. I'd like to look into the configuration of your API Key. Please send us an email at webservices@constantcontact.com with your API Key and the redirect URI you are passing through with your OAuth call. Regards, David B. Tier II API Support Engineer

David_B. · ‎10-31-2019

Hello, Thank you for reaching out to Constant Contact API Developer Support. Unfortunately there is not a way to view the contact-specific version through our API. That feature is currently only available in our website UI. I have passed along your feedback, as this could be a great feature enhancement. Please let us know if you have any other questions! Regards, David B. Tier II API Support Engineer

David_B. · ‎10-31-2019

Hello, Where are you being prompted to do this? Are you working in an app you are building, or are you using a 3rd party integration? Regards, David B. Tier II API Support Engineer

David_B. · ‎10-29-2019

Hello, Thank you for reaching out to Constant Contact API Developer Support. Can you clarify what you're looking to do? Are you using our V2 or V3 api? Regards, David B. Tier II API Support Engineer

David_B. · ‎10-29-2019

Hello, Thank you for reaching out to Constant Contact API Developer Support. Can you clarify what you're looking to accomplish? Our Authorization headers should be Bearer rather than Basic, and your access token is obtained during the OAuth flow. Are you using our V2 or V3 API? Regards, David B. Tier II API Support Engineer

David_B. · ‎10-24-2019

Hello, I wasn't able to find anything inherently incorrect with the body of your email. Assuming that you have verified the email address being used as the from/reply, that should also be okay. So taking a look at your sample, your payload is starting with an object called 'json', whereas the body should just contain the details. For example this: {'json': {'name': 'My new message-1571836258463'.... should instead look like this: {'name': 'My new message-1571836258463'.... with the closing bracket removed as well at the end. Please give that a try and let me know if you're still having trouble. Regards, David B. Tier II API Support Engineer

David_B. · ‎10-18-2019

Hello, That error in this case typically means that there isn't a contact with that ID in the account you are working with. Would you be willing to send an email to us at webservices(at)constantcontact.com with the Constant Contact username you are working in? I can do some digging and verify exactly why you're getting that error. Please let us know if you have any other questions! Regards, David B. Tier II API Support Engineer

David_B. · ‎10-17-2019

Hello, Thank you for reaching out to Constant Contact API Developer Support. The contact ID actually goes in your request URL and not as a header item. So for your example, you would make a call to: https://api.constantcontact.com/v2/contacts/1206033418/tracking?api_key=somekey And include your Authorization header (with the bearer token) along with it. This will return all of the tracking associated with this specific contact. Please let us know if you have any other questions! Regards, David B. Tier II API Support Engineer

David_B. · ‎10-15-2019

Hello Sveta, If you are seeing this data not going into the custom field and instead going into the street address, I would say that may be a possible bug. I'd like to research this a bit further in detail. Would you be willing to email us at webservices(at)constantcontact.com with an example of the body of your request, as well as the Constant Contact username that you are making the call to? Regards, David B. Tier II API Support Engineer

David_B. · ‎10-03-2019

Hello, Thank you for reaching out to Constant Contact API Developer Support. A 409 conflict usually comes up when you are trying to use something that is unique and already in use, such as an email address. Though I can't say for certain why you are seeing this on an individual update when making no changes at all. Since it seems to only be this one contact, I'd like to get more detail about them. Please email us at webservices(at)constantcontact.com with your Constant Contact username, and the email address for this contact and we'll be happy to take a closer look. Regards, David B. Tier II API Support Engineer

David_B. · ‎09-20-2019

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

David_B. · ‎09-18-2019

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

David_B. · ‎09-16-2019

Hello, Our V3 API is only able to be used with OAuth so there is no way to bypass the initial connection. However, once you have connected a Constant Contact account and received the initial access token and refresh token, you would use the refresh flow to exchange the refresh token for a new access token and refresh token without having to have the account owner log in again. Please let me know if you have any other questions. Sincerely, David B. Tier II API Support Engineer

David_B. · ‎09-16-2019

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

David_B. · ‎06-24-2019

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

David_B. · ‎05-16-2019

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

David_B. · ‎04-29-2019

Hello, Currently we do not have any SDK wrapper libraries for our new V3 API as our development focus is on building out additional features. You can find full documentation on our V3 version here: https://v3.developer.constantcontact.com/api_guide/getting_started.html Regards, David B. Tier II API Support Engineer

David_B. · ‎04-29-2019

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

David_B. · ‎04-24-2019

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

David_B. · ‎04-12-2019

Hello, Refresh Tokens do not expire the way that Access Tokens do. When using the Server flow, you are given a Refresh Token as well as an Access Token. When your Access Token has expired, you can exchange the Refresh Token for a new Access Token as well as a new Refresh Token. You would then continue doing this with the new Refresh Tokens obtained. Regards, David B. Tier II API Support Engineer

David_B. · ‎03-25-2019

Hello, Thank you for reaching out to Constant Contact API Developer Support. At this time you can only create an automated autoresponder email series within your Constant Contact account through the website UI. However, once this campaign is created, it would be sent to any contacts added to the list associated with it. This would work for any contacts added to that list, whether you add them manually in the UI, or use the API to add them. Our main support team is available to assist with any questions you have about setting up or using automated email campaigns. For details on how to create and schedule an autoresponder campaign, click here. Please have a look and let me know if you have any other questions! Regards, David B. Tier II API Support Engineer

David_B. · ‎03-13-2019

Hello, I completely understand your concern and your reasoning. Please email us at webservices@constantcontact.com and we will be sure to get an email out to you when we have a resolution. Regards, David B. Tier II API Support Engineer

David_B. · ‎03-11-2019

Hello, Thank you for reaching out to Constant Contact's API Support. Unfortunately I don't have any .NET code samples on this, however our OAuth process only requires the account owner connect once. They will get back an Access Token and a Refresh Token. Once you have these, you can programmatically use the refresh token to get a new access token without the need for the account owner to manually log in each time. If you wish to view our documentation our OAuth, see here: https://v3.developer.constantcontact.com/api_guide/server_flow.html Please have a look and let me know if you have any questions! Regards, David B. Tier II API Support Engineer

David_B. · ‎02-25-2019

Hello, Thank you for reaching out to Constant Contact API Developer Support. Unfortunately we do not have any SDK libraries for our new V3 API at this time. Right now all of our focus is on finishing additional endpoints to expand on the feature set of the V3 API. You can find our complete V3 API documentation at https://v3.developer.constantcontact.com/ and the API Reference section will have all of the necessary schemas you can expect. You can make calls to our API in .NET using something like HttpClient with the information showing in our documentation. Please let me know if you have any other questions! Regards, David Bornstein Tier II API Support Engineer

David_B. · ‎02-04-2019

Hello, Where are you getting that URL from? It appears to be wanting to use an API Key but is only being filled in with "XX". Regards, David B. Tier II API Support Engineer

David_B. · ‎01-25-2019

Hello, Thank you for reaching out to Constant Contact API Developer Support. Here is an example of what a call to obtain an access token might look like: string authorization_code = "{authorization code}" var client = new RestClient("https://idfed.constantcontact.com/as/token.oauth2?code="+ authorization_code +"&redirect_uri={redirect URI}&grant_type=authorization_code&client_secret={secret}"); var request = new RestRequest(Method.POST); string credentials = "{api key}:{secret}" byte[] plain = System.Text.Encoding.UTF8.GetBytes(credentials); base64cred = Convert.ToBase64String(plain); var base64auth = "Basic " + base64cred; request.AddHeader("authorization", base64auth); IRestResponse response = client.Execute(request); Note that this is what your app would do once the user is redirected to your app after allowing access during the OAuth process. You can use the RestRequest method to make other calls, such as POST calls to refresh the token. Please have a look and let me know if you have any questions! Regards, David B. Tier II API Support Engineer

David_B. · ‎01-14-2019

Hello, Thank you for reaching out to Constant Contact API Developer Support. It sounds like you might be trying to connect a 3rd-party app to your account and it is asking you for an API Key and access token. 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 integration 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 Please have a look and let me know if you have any other questions! Regards, David B. Tier II API Support Engineer

David_B. · ‎11-05-2018

Hello Greg, This information means that URL Query Parameters are not allowed within your registered redirect URI. You can use them in practice, they just can't be stored as a part of your registered redirect URI within Mashery. Regards, David B. Tier II API Support Engineer

David_B. · ‎08-27-2018

Hello Jason, Our SDKs are libraries that make it easy for you to make calls to our API. The calls themselves are run from your server with your own framework, so there is no update needed to the SDK directly. Because each web server and application is different, I'm not able to provide you with specific directions on how to make sure everything on your server is up to date. I would recommend reaching out to your hosting provider for detailed steps on how to check or upgrade your TLS compatibility. Sincerely, David B. Tier II API Support Engineer

David_B. · ‎08-06-2018

Hello, I do not think this issue is due to your placement of the autoloader/use statements. If that was incorrect, the error you would see would be a Fatal error: Call to undefined function as it tried to use the functions from our SDK. Also, you are getting back a CtctException which tells me that the SDK is installed. The error you are getting is "Bad Request" which means that there is likely something in the payload that is either unexpected, or malformed. I'd like to see a snippet of the code you are using to make your calls to Constant Contact, and if possible, a sample of all of the parameters you are passing through your function. For privacy, please send this via email to webservices@constantcontact.com and I'll be happy to take a look for you. Regards, David B. Tier II API Support Engineer

Re: Redirect_uri_mismatch

Re: Fetching email html content with dynamic conte...

Re: . addHeader("Authorization","Basic { access_to...

Re: About how to get campaign_activity_id

Re: . addHeader("Authorization","Basic { access_to...

Re: 400 Bad Request creating a new campaign

Re: V2 contact_Id and campaign_Id problems

Re: V2 contact_Id and campaign_Id problems

Re: V3 Bulk: Custom Field

Re: 409 response for endpoint: PUT /v2/contacts/{c...

Re: V3 .net Headless Server-to-Server Example

Re: Authorization error

Re: Beginner C# V3 API Example

Re: Authorization error

Re: Getting Mashery account associated with this ...

Re: HTTP 401 UnauthorizedException

Re: Is there any CC API PHP library for V3 ?

Re: Unicode in JSON refers to wrong code point

Re: Unicode in JSON refers to wrong code point

Re: Access token expired in V3

Re: How to create Email Automation Campaign Using ...

Re: API v.3 409 conflict on POST (create) a Contac...

Re: V3 .net Headless Server-to-Server Example

Re: V3 - Starter .NET Project

Re: invalid or missing authorization client id

Re: Beginner C# V3 API Example

Re: Access Token

Re: Setting up authentication but need a variable ...

Re: Support Ending for TLS v1.0 and v1.1- Immediat...

Re: Uncaught Exception Bad Request with PHP SDK