Hi @RobertH4988,
Our v3 API does have an authentication option; however it does not display the Access Token. You can go to the below page and when you click on any of the grey Oauth buttons to authenticate and use our API Tester page.
v3 API Reference
... View more
Hi @KimmellP9,
The official Constant Contact WordPress plugin does not need to go through this process. If you are having problems using the plugin I highly recommend to make a post on the support forums for that plugin specifically. You can find them located here: https://wordpress.org/support/plugin/constant-contact-forms/
... View more
Hi @TaylorC173,
Currently our oAuth is designed to only connect from one application to one Constant Contact account at a time. So what you are experiencing is by design. Your request/scenario has come up before and we are looking in to other options; however at this time we do not have one available.
Can you please provide more details for the use case as to why a single Constant Contact account would need to connect to more than one application/form? The more details/use cases we have the better we can work toward a solution.
... View more
Hi @user142486,
The "name" tag is not currently supported in our newest custom code editor. I have provided feedback to our engineers to see if we can get this tag added.
... View more
Hi @LucianoS94,
When using a third party integration you need to make sure that it can use custom fields that has specific names like gender. I believe Ninja Forms can. In this case you will want to make sure that you have created the custom field in your Constant Contact account and then make sure Ninja Forms allows you to map that same custom field in their interface.
Since this is a third party integration I would suggest to reach out to Ninja Forms directly to get instructions on how to map the fields correctly after you have created it in your Constant Contact account.
... View more
Hi @JamesC400,
You are most likely requesting the HTML content of an email campaign that was created in our 3G editor. The HTML content is not available through the API for these campaigns. Only email campaigns that are listed as "custom code" in the website UI will display the HTML content in the API.
... View more
Hi @ChrisC37,
The XML part is correct; we now use JSON format.
For the other question the answer is no. You would create an API Key and then use the oAuth flow so that your customers can generate an Access Token. We have two different oAuth flows; based on how you described your old application I would suggest the client flow as it is designed for a desktop application.
https://v3.developer.constantcontact.com/api_guide/client_flow.html
... View more
Hi @ChrisC37,
From what I can see things look good so far. I'm happy to check in to this further, but in order to do that I would need some information that is best kept private. I would suggest to email us at webservices(at)constantcontact.com and provide your API Key, Client Secret, and Redirect URI, so I can try to replicate.
... View more
Hi @WillH772,
I'm happy to check in to this, but in order to do that I would need some information that is best kept private. I would suggest to email us at webservices(at)constantcontact.com and provide your API Key, Client Secret, and Redirect URI, so I can try to replicate.
... View more
Hi @_Mystic_Chorale,
The tags option is not yet available in our v3 API. We did implement the segments option first and this would be a perfect way to use your contacts based on your description.
Concerning the endpoint you mentioned. That endpoint is more designed to replicate a sign-up form and that is why it is required to have a listID attached. You can still use that endpoint, but keep in mind that is not its designed use and there may be other issues such as accidentally resubscribing a contact; please read all of the documentation attached to that endpoint.
You can use our normal PUT to update a contact, or if you have multiple contacts you can use our BULK import method which is very similar to the endpoint you mentioned. https://v3.developer.constantcontact.com/api_guide/import_contacts.html
... View more
Hi @user984091,
You do not have to generate an authentication code more than once. Once you get the Access/Refresh Token for the first time I suggest you store that so it can be accessed when you need it to make an API call. You can then use the Refresh Token as needed to generated a new Access/Refresh Token and replace those with your original set that you stored.
... View more
Hi @JustinZ21,
The server flow refers to an application that is server side application versus a client side application such a mobile app.
If your Refresh Token is getting invalidated that is most likely due to generating another set of Access/Refresh Tokens for the same account.
... View more
Hi @LadonnaW91,
We can try to do more troubleshooting, but the information we need would be of a more private nature. I would recommend to reach out to us using webservices(at)constantcontact(dot)com.
... View more
Hi @TracyS783,
That error is indicating that whatever you are trying to do is not allowed due to the CORS policy. If you are using our API this makes sense because our API does not use CORS. If you are using something other than our API can you please specify what you are using?
... View more
Hi @user245131,
It looks like the characters are being converted due to the character set not being supported. Please keep in mind that we support 8-bit character sets and the accents in the example you gave appear to have come from a language that uses a 16-bit character set; which is also sometimes referred to as Unicode.
Can you confirm what language and/or character set you are attempting to use?
... View more
Hi @SharlaM82,
Since Constant Contact did not create this integration we are very limited on the support we can offer. I'm not familiar with that integration directly. Does the creator of the integration offer any setup instructions or guides? Have you tried reaching our to their support for further guidance?
... View more
Hi @KevinW745,
I was able to update a contact using that endpoint without error. We'd be happy to look in to this issue further. Due to needing the email address for research I would suggest you email us at webservices(at)constantcontact(dot)com with the details of your API call.
... View more
Hi @TestingA64,
Due to the nature of some of the private information we need to troubleshoot this we have sent you an email requesting that information.
... View more
Hi @LizzetteC0,
At this time the oAuth flow listed in our documentation is the only option. We are researching other options; however we do not have an ETA for any of them.
... View more
Hi @SeanS723,
Yes; when you go through the Refresh flow in Step 5 of oAuth the Access Token and Refresh Token are both generated new. You will want your program to read the new values and plug those in to the appropriate places. It sounds like you are already storing the Refresh Token somewhere; hopefully it should be something you can do to just grab it from the response when you also grab the new Access Token and store them both.
... View more
Hi @user978014,
It sounds like you are referring to the from and reply-to addresses when sending an email campaign. These are not set dynamically; they are set in the header section of the UI, or if you are using the API they have a data pair where you set them. Each individual email campaign can have a different value, but please keep in mind when sending an email campaign every person who receives it will see the same email address that you have set for that one campaign.
... View more
Hi @LarryV375,
I reviewed the files sent and it appears you are trying to do a POST to the endpoint /v2/contacts/{contactID} and this endpoint should be a PUT instead.
... View more
Hi @Goldrush,
In order to fully research the issue we will need some private information. We will reach out to you in a private case/email.
... View more
Hi @user5921094,
The character set you are specifying is fine; however are you including any actual characters in the text you are submitting that is outside of the standard character set allowed by the one you are specifying?
... View more
Hi @saraw7349,
The redirect_uri needs to match the setting in your API application as well as in your integration. I would encourage you to check our API documentation to ensure your oAuth flow is set correctly.
You did not mention which version of the API you are using so here are the current URLs to both versions.
v3: https://v3.developer.constantcontact.com/
v2: https://developer.constantcontact.com/
... View more
Hi @NoahK,
This has happened to another user; while we are still investigating the reason behind the problem we have found a work around.
You can create a completely new Mashery account and create a new API Key/Access Token. This new information will let you get back up and running.
... View more
Hi @user5921094,
Our system uses UTF-8, or 8-bit character set. If you are receiving this error you are most likely using a character set that is not supported. Can you verify if you are using a different character set?
... View more
Hi @DonaldD14,
We have looked in this internally and there are two things going on with your scenario.
First of all the update_source should be listed as Account. Since this is restoring a deleted contact this needs to be done by the account owner and not the contact themselves. The update_source would be Contact if you were restoring an unsubscribed contact.
The second issue is that there was a problem with the data for that specific contact. This has been updated in our database.
Please let us know if you continue having issues after this.
... View more
