About Jimmy_D

Hi @PaulK4625,   I believe you also sent us an email. It appears there is a difference in our documentation/schema. One endpoint uses street_address and the other uses street_addresses. For the /sign_up endpoint you will want to use street_address and this should work. I've already reached out to our engineers to see how we can best address this. ... View more

Hi @JoyceM998,   I also wanted to mention that a server to server oAuth is not required for this type of integration. If you set up our current oAuth correctly it will only require the Constant Contact account owner to grant access once and the rest can be automated. ... View more

Hi @Goldrush and @HeidiS146,   We did not have a server issue today. If you see this issue again can you please let us know what endpoint you calling? ... View more

Hi @PaulK4625,   Here is a screenshot of how I have my POSTman setup.     curl --location --request POST 'https://idfed.constantcontact.com/as/token.oauth2?code=code&redirect_uri=https%3A%2F%2Flocalhost&grant_type=authorization_code' \ --header 'Authorization: Basic {base64encoded clientID:clientsecret}' ... View more

Hi @MeirH0,   The API cannot edit a campaign template; however it schedule/send, and view reporting for those campaigns. If you are going through the steps to create the campaign in the UI what is the use case to then try to get the HTML and put it back in our system? Once I understand the use case I may be able to offer a better solution. ... View more

Hi @user71531,   This endpoint is one we are still working on and will be added in the future. We don't have an ETA yet; however you can check our Release Notes for when we add new endpoints. ... View more

Hi @JohnD2205,   You haven't provided a great description of your app platform, but I'm guessing that those users will end up becoming contacts in the Constant Contact account, so no those people do not need a CTCT account and do not need to grant access.   Only the owner of the Constant Contact that will be adding the contacts needs to grant access. ... View more

Hello @MartinC966,   Thank you for reaching out to Constant Contact's API Support.   If you are making a POST then the JSON data format is correct and I would look in to either your header information or how you have your endpoint URL formatted.   ... View more

Hi @JohnD2205,   Currently you must go through the oAuth flow. We are looking in to other options; however at this time those other options have not been released. ... View more

Hi @MarianN3,   If you are using the Constant Contact pop-up form then if you add the universal code to a webpage the form will pop-up. It should not matter what page it is on. This means you do not want to add the universal code to a widget that is on all pages because the form will pop-up on all pages. Add the code to only the one page where you want the form to show.   If you are having difficulty with adding the universal code to your website you may want to reach out to your hosting company for assistance. ... View more

Hi @SarasD,   The error code for that should be 403. ... View more

Hi @BobB692,   The Access/Refresh Tokens do have a link between the API Key that generated them and the account that authorized them. If you were to create a new API Key and go through the oAuth flow it should generate a completely different set of Access/Refresh Tokens that do not interfere with the first set. ... View more

Hi @BobB692,   This is correct; the scenario you have outlined to use the same account on multiple sites is something we are looking in to for future development and do not currently have an ETA on. ... View more

Hi @GaryB873,   Our Marketplace has a services section that lists companies offering various types of services. If you go there and search for "API" or "developer" you should find a listing with companies familiar with our API. ... View more

Hi @ChristianZ825,   I can understand your frustrations when a company implements new changes, but I assure you they are for good reasons. We changed our Access Tokens to expire sooner to help ensure higher security. While not everyone appreciates the extra security we have notice a decrease in bad actors compromising accounts.   When using the v3 API your Access Token can expire anywhere between two hours and 24 hours depending on use. When you generate the Access Token you also generate a Refresh Token; the idea is that you store both of these tokens. You use the Access Token to make your API calls and when it does finally expire you then use the Refresh Token to generate a new set of Access/Refresh Tokens and this is Step 5 in the oAuth flow. As long as you do not go through the other steps your Refresh Token will never expire of be invalidated. ... View more

Hi @ChristianZ825,   Please keep in mind that our v3 API is the focus of our development. The SDKs for our v2 API are not being updated and the v2 API itself will be receiving only critical updates. Our v3 API does have code samples for each of the endpoints that are currently released. ... View more

Hello @JamesC400,   Thank you for reaching out to Constant Contact's API Support.   That error means one of two things. Either the API Key you are using in invalid; which doesn't seem likely since you are able to generate your authorization code, or the authorization header you are using was not generated correctly.   In Steps 4 and 5 of the oAuth flow you need to include an authorization header that uses a Basic token and the way you generate that is by putting your api_key and client_secret together separated by a : (colon). Then base64 encoding that.   Here is an example of how the header would look if I were to be submitting a cURL command and encoded api_key:client_secret.   header 'Authorization: Basic YXBpX2tleTpjbGllbnRfc2VjcmV0' ... View more

Hello @SatishB721,   Thank you for reaching out to Constant Contact's API Support.   I tested this and despite our example text it does require that you have a timestamp listed as well. I tried with start=2015-09-01T00:00:00-0500&end=2020-04-05T00:00:00-0500 and it worked just fine. I'll double check with our backend and see why the time is required despite our documentation. ... View more

Hello @SupremeQ,   Thank you for reaching out to Constant Contact's API Support.   Can you show me a screenshot of it running twice, or give me the activity IDs?   Regards, Jimmy D. Tier II API Support Engineer ... View more

Hello @DMIMarketing,   Thank you for reaching out to Constant Contact's API Support.   You would not want to hard code the Access/Refresh Tokens as the Access Token does expire. You would want to store the tokens somewhere and then use a variable in your code to pull the token. The refresh flow is used to generate a new Access Token when needed.   Regards, Jimmy D. Tier II API Support Engineer ... View more

Hi @SteveA3416,   The URL you have listed doesn't make sense to me. If that is your redirect URI then you should not have the other parameters in it such as access_token and token_type (unless those are part of your own website, but that does not seem to be the case).   Or that is the URL that is returned to you in Step 4 which also does not make sense as the URL that will make the return will also be from idfed.constantcontact.com.   I'm happy to troubleshoot this; however some of the information might need to be kept secret for security reasons. You can reach out to use at webservices(at)constantcontact(dot)com. ... View more

Hello @KathleenH522,   Thank you for reaching out to Constant Contact's API Support.   The two versions of our API are not cross compatible so you are correct that you cannot use Mashery to get a v3 Access Token.   Make sure when you use the redirect URI in your oAuth call that it needs to be encoded. This means that if your redirect URI is https://localhost it should look like https%3A%2F%2Flocalhost in your API POST call. Here is a full breakdown of what it would look like when using POSTman.   step 1 - auth request URL https://api.cc.email/v3/idfed?client_id={api_key}&redirect_uri={encoded redirect_uri}&response_type=code&scope=contact_data+campaign_data+account_read+account_update   step 2 - use request URL put above URL in your browser, login with CTCT username/password, click Allow   step 3 - authorization code grab authorization code from browser URL   step 4 - exchange code for tokens (header) Authorization Basic api_key:client_secret (base64 encoded) https://idfed.constantcontact.com/as/token.oauth2?code=(authorization_code)&redirect_uri={encoded redirect_uri}&grant_type=authorization_code   step 5 - refresh token (header) Authorization Basic api_key:client_secret (base64 encoded) https://idfed.constantcontact.com/as/token.oauth2?refresh_token={refresh_token}&grant_type=refresh_token ... View more

Hello @AlbertS183,   Thank you for reaching out to Constant Contact's API Support.   You can use our API which is a standard RESTful API that accepts HTTP requests. This means you can just make direct calls to the API if you are more comfortable with that. You can find our documentation here. ... View more

Hi @JessicaG921,   The oAuth flow does require a user to allow access to the Constant Contact account. Even if the account that is being used is your own account you have to allow your program access to the account once. ... View more

Hi @ttt24,   Please check this page and specifically look at the schema for the update_source. ... View more

Hello @RohitS849,   Thank you for reaching out to Constant Contact's API Support.   We are looking in to a server to server option, but at this time this is the only authentication option available. I'm not sure why you say that this is not a one time step. Once you get the Access/Refresh Token the first time you will not need a human to login and click the Allow button again. You will need to refresh the tokens, but that process can be automated without human interaction. ... View more

Hello @NCJTC,   Thank you for reaching out to Constant Contact's API Support.   Step 1 from the server flow will end up redirecting you to the URL that is in your redirect_uri which is a website. If you used http://localhost then it will be a blank website that will have a generic error message; however the URL will have the authorization code appended. I've included a screenshot of what you will see below. The reason this does not work in POSTman is because POSTman does not display websites (at least I have not been able to get them to display).   ... View more

Hello @JessicaG921,   Thank you for reaching out to Constant Contact's API Support.   You did not mention which version of the API you are using; however both versions work the same. Initially there is a requirement of the user logging in to the Constant Contact account and clicking on the Allow button. Once that has happened there is no need for further user interaction regardless of which API version you are using. ... View more

Hello @MJ313,   Thank you for reaching out to Constant Contact's API Support.   Currently neither version of our API has access to A/B emails. It will be adding to the v3 API; however I do not have a release date for this feature yet.   The tracking summary will be released for the v3 API. The release date is also not yet available, but you can keep an eye on our v3 Release Notes for when we add new endpoints and updates. ... View more