About Jimmy_D

Jimmy_D · ‎10-01-2019

Hello @PaulH035, Thank you for reaching out to Constant Contact's API Support. Our API can provide the reporting data; however the data would be provided in a JSON response and not in a csv file. You would need to take the data and add it to a csv file on your end. Currently all of the reporting endpoints are available with our v2 API and our v3 API will have the reporting endpoints released over a few releases still.

Jimmy_D · ‎09-30-2019

Hello @AdamM5071, Thank you for reaching out to Constant Contact's API Support. We appreciate you bringing this to our attention. We'll go over the possibilities and update the file as needed and get back to you.

Jimmy_D · ‎09-30-2019

Hi @GRRA, That error message occurs when the Refresh Token you used was invalidated by generating another Refresh Token. When using the oAuth flow you would generate one Access/Refresh Token for a single Constant Contact account and then use that Refresh Token to generate a new Access/Refresh Token. When you generate the new Access/Refresh Token this will invalidate the previous tokens.

Jimmy_D · ‎09-24-2019

Hi @JonA63399, You can do a GET to see a deleted contact. You must include the email address and you must include a status of either all, or deleted. This will return a result of the contact that looks like this. "contacts": [ { "contact_id": "d4e514d4-9d0b-11e9-9bfe-d4ae528e486a", "email_address": { "address": "msm005@ucsd.edu", "permission_to_send": "implicit", "created_at": "2019-07-02T16:56:17-04:00", "updated_at": "2019-09-09T11:56:37-04:00", "opt_in_source": "Account", "opt_in_date": "2019-07-02T16:56:16-04:00", "confirm_status": "off" }, "first_name": "Micaela", "last_name": "Martinez", "create_source": "Account", "created_at": "2019-07-02T16:56:17-04:00", "updated_at": "2019-09-09T11:56:37-04:00", "deleted_at": "2019-09-09" },

Jimmy_D · ‎09-12-2019

Hello @GregC245, Thank you for reaching out to Constant Contact's API Support. Once you have obtained your Access Token you want to send that with your API calls as the Authorization Bearer token. How are you using your the Access Token in your call?

Jimmy_D · ‎06-26-2019

Hello @YosvaniA, Thank you for reaching out to Constant Contact's API Support. Our system does a soft delete of contacts which means the email address still technically exists in the account. In order to use it again instead of creating that contact with a POST you would update it with a PUT. If you are using our v2 API then you would use this endpoint. https://developer.constantcontact.com/docs/contacts-api/contacts-resource.html?method=PUT

Jimmy_D · ‎06-20-2019

Hi @VC1977, This thread is several years old and refers to our v1 API which is deprecated. Are you using the v1 API and encountering this issue, or are you using our v2 or v3 API? If you are using our v1 API I would highly recommend to look in to updating to one of our other versions.

Jimmy_D · ‎06-03-2019

Hello @VAFBM, Thank you for reaching out to Constant Contact's API Support. Based on our settings/documentation and testing; the Refresh Token does not expire. Please keep in mind our production tokens have not gone more than 12 months, but they are not supposed to expire.

Jimmy_D · ‎05-20-2019

Hi @DanielC171 and @ArthurB21338, If you are receiving this error still then it would be due to an issue with the call or the data being sent as we are not currently experiencing a system issue that would cause this. I would verify that your code is correctly retrieving the Access Token and you can make a call with a new Access Token then attempt going through the refresh flow. If the error only occurs after going through the refresh flow verify that you are correctly replacing the old Access Token with the new Access Token. If you are still having issues it would be beneficial to see a code snippet. Generally we recommend to email us at that point (webservices@constantcontact.com); however you are welcome to post the code here as well.

Jimmy_D · ‎04-22-2019

Hi @KenJ32, Previously we only had endpoints for contacts. We recently released new endpoints for email campaigns. Since that release the scopes moved from optional to required. The release notes mention the new scope, but it does not mention they are now required. We'll work towards making our notes better going forward.

Jimmy_D · ‎04-22-2019

Hi @user37310, Thanks for reaching out to Constant Contact's API Support. You emailed us for support on this and since it can contain some sensitive information we will continue our work in those private emails. I also edited your original post to remove your API Key from public view.

Jimmy_D · ‎04-22-2019

Hi @AprilD761, Your code looks correct. You would get an error if somehow the $refreshToken was accidentally pulling in the Access Token instead of the previous Refresh Token. Since we cannot see the rest of the code I would ensure it is pulling in the correct value.

Jimmy_D · ‎04-16-2019

Hi @IntegrationT4 and @ERICW916, You can use a wildcard when setting the redirect URI in the application settings of your API Key. Then when you use the redirect URI in your actual call it will work with different parameters. Here is an example. In the settings for your API Key set this as your redirect URI. https://localhost?id=* When you add the redirect URI to the API call endpoint you can use different parameters in place of the wildcard. https://idfed.constantcontact.com/as/token.oauth2?code={authorization_code}&redirect_uri=https://localhost?id=5&grant_type=authorization_code Your redirect URI will need to be encoded of course.

Jimmy_D · ‎04-11-2019

Hi @SteveF71468, Regardless of the version of the API you are using you will want to use the oAuth flow to generate an Access Token. It sounds like you are using the v3 API if your token is expiring after a day. If this is the case you will want to make sure you include the refresh portion of the oAuth flow. v2 oAuth: https://developer.constantcontact.com/docs/authentication/oauth-2.0-server-flow.html v3 oAuth: https://v3.developer.constantcontact.com/api_guide/server_flow.html

Jimmy_D · ‎04-11-2019

Hello @APHSA_VA , Thank you for reaching out to Constant Contact's API Support. Constant Contact has not created a first party integration with iMIS. I also did not see one listed on our marketplace. If you want to look in to having the integration developed you can either approach iMIS directly or you can again check out our marketplace to hire a developer. https://marketplace.constantcontact.com/

Jimmy_D · ‎04-11-2019

Hello @AprilD761 , Thank you for reaching out to Constant Contact's API Support. If you continue going through the oAuth documentation for v3 you will notice that it mentions a Refresh Token section after the Access Token section. You use the Refresh Token to get a new Access Token. You can find this documentation here.

Jimmy_D · ‎04-04-2019

Hello @MattK9938 , Thank you for reaching out to Constant Contact's API Support. Your code does look correct to me. I just went through POSTman and gave it a shot as well to make sure everything is working. I was able to get a valid response back. Here is my POST displayed as PHP cURL. Can you provide the full code snippet and not just that one body section? Maybe there is something in another section causing an issue. <?php $curl = curl_init(); curl_setopt_array($curl, array( CURLOPT_URL => "https://idfed.constantcontact.com/as/token.oauth2?code=PKxX_IGvP06o24xOh3-UuEqWcncwyWhTl9ViaAEt&redirect_uri=https%3A%2F%2Flocalhost%2F%2A&grant_type=authorization_code", CURLOPT_RETURNTRANSFER => true, CURLOPT_ENCODING => "", CURLOPT_MAXREDIRS => 10, CURLOPT_TIMEOUT => 30, CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1, CURLOPT_CUSTOMREQUEST => "POST", CURLOPT_POSTFIELDS => "", CURLOPT_HTTPHEADER => array( "Authorization: Basic (base64-APIKey:ClientSecret)", "Postman-Token: 6a82b9b6-7657-409a-b481-4e0e65a5f722", "cache-control: no-cache" ), )); $response = curl_exec($curl); $err = curl_error($curl); curl_close($curl); if ($err) { echo "cURL Error #:" . $err; } else { echo $response; }

Jimmy_D · ‎03-06-2019

Hello @Happiness, THank you for reaching out to Constant Contact's API Support. The Contact Form 7 Integration is created by Contact Form 7 themselves and so the support we can provide is extremely limited. If you have already connected the integration to your Constant Contact account that is about as far as I could go. Any other set up would be beyond what our knowledge of the integration entails. You can check on their website for support information. https://contactform7.com/docs/ You can also look in the upper right of that website for a link to their support forums to post a question or read questions by other users. Perhaps your question has already been answered. I did try to find the specific steps to select a list, but I was not able to find them.

Jimmy_D · ‎03-01-2019

@Fetzer, You can do a PUT to update the deleted contact. You would just need to ensure you use the "update_source": "Contact" to tell the system that the contact is taking the action. The 409 conflict is technically describing a conflict between the status of express versus implied status on the contact. The action being used to change is being done by the account owner when the email address has express permission and only actions can be taken by the contact themselves. This is generally done with sign-up forms when a contact has been unsubscribed in addition to being deleted.

Jimmy_D · ‎02-27-2019

Hi @MatthewB2133, This post is specifically referring to someone using our API to create their own sign-up form. If you are looking for a sign-up form that you do not need to write the code for yourself you can check out the link at the top of your Constant Contact account. If you need assistance with using those sign-up forms I would highly recommend to call our support department at 866-289-2101.

Jimmy_D · ‎02-27-2019

Hi @InteractiveK, Thank you for reaching out to Constant Contact's API Support. We are currently researching this issue and working toward a solution. What is happening is what you alluded to; the email address is a deleted contact. You can do a GET on the status of DELETED and not the specific email address. This will return all deleted contacts and you should see the email address in question among those results. That would be the work around I would recommend for now until we have a full resolution in place. If you would like to be notified of the resolution by email feel free to contact us at webservices@constantcontact.com to request this.

Jimmy_D · ‎02-27-2019

Hi @user88222, Thank you for reaching out to Constant Contact's API Support. I have sent you a separate email; please look for it at the email address attached to your Constant Contact account.

Jimmy_D · ‎02-21-2019

Hi @user845116, I apologize about that. I did not notice the spelling errors. I will get this to our documentation person and have it corrected. I'll let you know when it is so you can then update your code again to the corrected versions.

Jimmy_D · ‎02-18-2019

Hi @user845116, Are you able to make this call using the API Reference page?

Jimmy_D · ‎02-13-2019

Hi @user845116, I've done various testing and the only way I can replicate this exact error message is when submitting to the incorrect URL i.e. https://api.cc.email/v3/activities/add_list_membership instead of https://api.cc.email/v3/activities/add_list_memberships. If I submit the call with an invalid listID I receive an error calling out the invalid listID. If I submit with a non-existing contactID I receive a 201 due to the bulk request being successfully made, but there is no activity actually taking place. I know your post shows the correct URL, but can you please verify there is no leading or ending spaces or anything along those lines?

Jimmy_D · ‎02-12-2019

Hello @user845116, Thank you for reaching out to Constant Contact's API Support. I would suggest to take a look at our API Reference page to see a full example of what could be in the body for creating a contact. You do need to include "create_source": "Account" or "create_source": "Contact" depending on whether you want the contact to reflect if it was created by the account owner or created by the contact. The last option is generally used for sign-up forms. You also need your email address to be in the form of an array. I'm not sure exactly how you had it coded, but here is what it should look like in JSON. { "email_address": { "address": "gum2@testing.com" } Here is the full JSON for what I added to my own test account. { "email_address": { "address": "gum2@testing.com" }, "create_source": "Contact", "list_memberships": [ "17d13e10-9550-11e6-84df-d4ae5275b546" ] } Your listID will of course be different.

Jimmy_D · ‎01-22-2019

Hello Everyone, Sorry for the delayed response. As I'm sure you are already aware this issue has been resolved. We had a temporary issue with some certificates and they have been updated. Please let us know if you still see this problem.

Jimmy_D · ‎12-31-2018

Hi @ChrisB73, Using the I/O-docs page is still technically input from the user of the account; in this case you did the interaction and then probably hard coded the Access Token. To be more secure we have lowered the expiration time of the Access Tokens from 10 years (v2 timeout) to 24 hours (v3 timeout). If you write your program correctly you can still do the customer input yourself and generate an Access Token which will then automatically refresh every 24 hours using the refresh portion of oAuth. Instead of harding coding these now you will just need to write the code to have them changed out. If you need assistance with this feel free to reach out to us at webservices@constantcontact.com.

Jimmy_D · ‎12-31-2018

Hi @ChrisB73, Thanks for reaching out to Constant Contact's API Support. The v2 API also required the user's input to authorize. This seems to be a common misperception between the two APIs and I believe the reason for this is with our v2 API you could generate an Access Token that lasted for a very long time. However; to generate the Access Token you still needed the user's Constant Contact username/password which is the exact same requirement in our v3 oAuth. The only difference between oAuth in v2 and v3 is that our v3 Access Tokens expire after 24 hours and has to be refreshed. This does not require any extra user input. If you have the Access Token already then you can refresh it automatically. I have to ask how did you get an Access Token for your v2 API sign-up form without the Constant Contact username and password?

Jimmy_D · ‎11-26-2018

Hi @ERICW916, I have brought this up to our engineers and they are looking in to it. At this time I do not have an ETA; however if you would like an email when the issue is resolved you can email us at webservices@constantcontact.com and we can set that up.

Re: "Dig Deeper into My Reports" style report via ...

Re: Supported Values of EmailAddress API property...

Re: Refresh Token

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

Re: Authorization error

Re: Adding deleted contact

Re: (500) Internal Server Error

Re: Refresh Token

Re: HTTP 401 UnauthorizedException

Re: API V3 403 Forbidden

Re: mashery.not.authorized.inactive and The Masher...

Re: Access token expired in V3

Re: Authorization Code Request: 400 - Invalid redi...

Re: v2 or v3 API for very basic integration?

Re: iMIS Cloud integreation

Re: Access token expired in V3

Re: oAuth2.0 Server Flow in V3 API

Re: Contact Form 7 Intergration: Sending signups t...

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

Re: Customize sign up form

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

Re: Authorization Code Request: 400 - Invalid redi...

Re: API v3 Creating contact invalid email address

Re: API v3 Creating contact invalid email address

Re: API v3 Creating contact invalid email address

Re: API v3 Creating contact invalid email address

Re: HTTP 401 UnauthorizedException

Re: v2 or v3 API for very basic integration?

Re: v2 or v3 API for very basic integration?

Re: Authorization Code Request: 400 - Invalid redi...