About Jimmy_D

Hello @ttt24,   Thank you for reaching out to Constant Contact's API Support.   That error in general means the contact is in a state where you cannot change it; only the contact can make changes to their profile. This usually occurs when they have explicitly updated themselves via a sign-up form.   If you need to change the contact's information you will need to perform the action as if you were the contact instead of doing it as the account owner. If you mention which version of the API you are using I can point you to the correct documentation page. ... View more

Hello @JamesV628,   We know there is a lot of requests for server to server authentication. This is something we are looking in to; however at this time we do not have this option available. ... View more

Hi @AnthonyA535,   Trial users do have access to our API, please keep in mind your trial account may expire and then you will not be able to access your Constant Contact account.   Using the API for any reason, including a sign-up form, requires using the oAuth flow. We have some small code snippets of PHP under each endpoint, but it is not a full sign-up form/integration. As for adding reCaptcha I can tell you that it will work with our API. You will need to reference their documentation to ensure you write the code correctly. ... View more

Hello @AndrewW49925,   Thank you for reaching out to Constant Contact's API Support.   Both of our API versions require an initial user interaction to login to the Constant Contact account and click the Allow button. Once that happens once you get an Access Token. The difference is when the Access Token expires. In our v2 API the token is not super secure in that it expires after multiple years. In our v3 API the token expires after 24 hours. When using our v3 API you also get a Refresh Token to refresh the Access Token when it expires, this does not require the user to interact. ... View more

Hello @PREPARE79,   Thank you for reaching out to Constant Contact's API Support.   Our API currently has a single method of authentication with oAuth2 and that is with generating an Access Token. If this process is only going to be seen by you then you can use https://localhost as the redirect URI which will direct you to a generic website.   We are exploring other options to our authentication, but at this time we do not have an eta on those options. ... View more

Hello @AnthonyA535,   Thank you for reaching out to Constant Contact's API Support.   Our v3 API is our newest version and will be including new features and products that our v2 API does not include. ... View more

Hi @JulieK7237,   Option 3's only down side really is the rate limit. If that is not an issue with your integration then feel free to use it. ... View more

Hello @JulieK7237,   Thank you for reaching out to Constant Contact's API Support.   The contactIDs are not currently included in the results of the BULK import; I'll talk with our engineers to see if that is an option.   Your best way to get those IDs with the fewest amount of calls is to do a GET an include the parameter of either a specific listID (if you created a new list), or use the parameter of updated_after. Either new, or updated, contacts will display with the updated_after parameter which will limit your results and help you see only specific results; assuming you do this GET after you finish your import.   https://v3.developer.constantcontact.com/api_reference/index.html#!/Contacts/getContacts ... View more

Hi @AjayS62,   We are reviewing this option, but at this time we have no ETA. ... View more

Hi @JulieK7237,   The process you described under question 1 is what I use when I'm testing with POSTman. I manually put together that URL you wrote out, paste it in to my browser, and get back the authorization code. Then you have 60 seconds to use that code to generate your Access/Refresh Token. Once you have the Access/Refresh Token you should not ever have to go through the process to get an authorization code again.   As for your second question; you should only be prompted to click the Allow/Deny button once. If it ever comes up again it should be due to generating a new Secret, using a new Constant Contact account, or using a new API Key. Assuming you continue to use the same pieces of information that step should not repeat. ... View more

Hi @JulieK7237,   The terminology for the UI is more focused on an end-user that is not familiar with our API and programming integrations. I can bring this up to our Product Owners and see what we can do to make everything more consistent. ... View more

Hello @CarolynG105,   Thank you for reaching out to Constant Contact's API Support.   The JSON you are sending contains all of the elements and some of the are mutually exclusive with others. Please check our API Reference page and look to the right side for the Body Schema to review which items are mutually exclusive. ... View more

Hello @HonestA,   Thank you for reaching out to Constant Contact's API Support.   If you have not reached out to us at webservices(at)constantcontact.com then please do so as this will require some information that is best kept out of the public eye. ... View more

Hello Everyone,   Thank you for reaching out to Constant Contact's API Support.   We are looking in to other options to authenticate. As of right now you will need to go through the oAuth flow listed in the v3 documentation to get the Access Token and Refresh Token. Please keep in mind the need to enter the Constant Constact username/password and clicking Allow/Deny only occurs once. After you do that you just need to track/save the Access and Refresh Tokens. ... View more

Hi @JulieK7237,   I've noted your interest in the B2B oAuth. This is something we are looking in to.   In regards to how you do the login/allow portion; we generally think that is going to occur when the user of the integration (in this case you are the developer and the user) first installs the integration to their website.    Let's take this scenario. The integration is a sign-up form that is being created for use by anyone (this includes yourself). You've finished development and have made the integration available to users to install on their website. Once the integration is installed the user needs to connect the integration to their Constant Contact account. They are then prompted to enter their un/pw, click allow, and now everything is connected. Now behind the scenes the Access/Refresh Token is renewed automatically as needed using whatever method you decide (timers or refreshing before every call, or waiting for an error response then refreshing).   We understand that many developers are requesting a server to server oAuth, but at this time we do not have an option for that. We are looking in to it, but until then the oAuth was designed around a user providing the un/pw and clicking allow. ... View more

Hello @PaulaW79,   Thank you for reaching out to Constant Contact's API Support.   As mentioned by another user here we are currently not creating any SDKs while we finish developing our v3 API. Once we have completed the v3 API we will look in to the possibility of SDKs, but we have not made any decisions yet. ... View more

Hello @BradL9,   Thank you for reaching out to Constant Contact's API Support.   If you are using the inline, or pop-up, forms provided from within your Constant Contact account then these forms cannot be modified beyond what options are available in your account.   The agent might have been thinking that once you put the form on your website you might be able to edit the HTML directly, but that can potentially cause problems if you later update your form. ... View more

Hello @PanamplifyA,   Thank you for reaching out to Constant Contact's API Support.   A/B campaigns are a different type of campaign that is not currently included in the v3 API. It is on the schedule to be included; however I do not have a timeframe I can provide yet. It is one of our higher priorities as far as new reporting endpoints though. ... View more

Hello @edivodev,   Thank you for reaching out to Constant Contact's API Support.   We do have this mentioned on the API Reference page for making a PUT to a contact. It is in the paragraph at the top of that section. However; I do think we can do a better job of pointing this out and I'll work with our website/documentation folks to see what we can do about that. https://v3.developer.constantcontact.com/api_reference/index.html#!/Contacts/putContact   Basically if it is not a sub-resource and the field is not included it will be set to a null value. ... View more

Hello @AKIRAK3,   Thank you for reaching out to Constant Contact's API Support.   You can email us at webservices(at)constantcontact(dot)com. Please include the API endpoint you are calling, the payload, the API Key, and if possible the Constant Contact username in your email to us. ... View more

Hello @EneaG,   Thank you for reaching out to Constant Contact's API Support.   The Refresh Token does not have an expiration date; however it can be made invalid if another Refresh Token is generated.   When you create your first Refresh Token it will remain active and valid as long as it is the only Refresh Token. If for some reason you generate another Access/Refresh Token using the oAuth flow that will invalidate the first Refresh Token. ... View more

Hello @pdub,   Thank you for reaching out to Constant Contact's API Support.   You have the information correct. At this time our oAuth2 flow does require user interaction once to type in the username/password of the Constant Contact account that you are sending your email addresses to, and to click the Allow button. Once this is done you will only be dealing with the Access Token and Refresh Token which does not require user interaction.   The Access Token can expire in one of two ways. It will expire after two hours if it is not being used, or it will expire after 24 hours even if it is being used.   Generally we recommend to use a local database to store your Access Token and Refresh Token so you can access these whenever you need them. Also many of our developers have found using a form of timer to refresh the tokens has been useful instead of waiting for an error code.   An example of the timer would be to set one timer for 24 hours and another timer for two hours. The two hour timer resets every time an API call is made. If either timer reaches its end then your program goes through Step 5 in the oAuth flow which is the step to refresh and get new Access/Refresh Tokens.   There have been several requests for an oAuth flow that does not require any user interaction for server to server applications. This is something we are reviewing, but we have not made any decisions on yet. ... View more

Hi @edivodev,   Due to the holidays we are on a code freeze which means there will be no changes made. I'll see if I can get an update for after that timeframe. ... View more

Hi @GregB1741,   The wildcard can be placed anywhere in the redirect URI. ... View more

Hello @edivodev,   Thank you for reaching out to Constant Contact's API Support.   It seems our v3 API does not like your HTML, but our v2 API and as you already noticed our UI accept it just fine. I've brought this to our engineers attention and we'll look in to it. ... View more

Hello @PrincessDS,   Thank you for reaching out to Constant Contact's API Support.   If you are using the same format and getting an error than something with the data is causing the problem. To keep your data secure you can email us at webservices(at)constantcontact(dot)com and we'll take a look in to it. Please include any relevant information. ... View more