About ChrisC37

Courtney_E · ‎04-12-2022

Hello Chris, Thank you for reaching out to Constant Contact API Developer Support. We appreciate your concerns for security, and have followed up directly via email to your original case #29711852, as well as with some detailed instructions in reply to your follow up inquiry (case #29726297), but I wanted to close the loop here as well. Applications that integrate with Constant Contact must use the OAuth2 authorization protocol to securely authenticate a Constant Contact user account, and to be granted access to that user's data. To provide improved security, Constant Contact is now using a new authorization management service, and will be ending support for the previous service/keys on March 31, 2022. This means that all new V3 API keys generated through the My Applications page within the Developer Portal (https://app.constantcontact.com/pages/dma/portal/) will not be compatible with applications/integrations/plugins that have not yet been updated by their developers. Additionally, if the developer does not update their application, existing API keys will no longer be supported by Constant Contact as of March 31, 2022. For more details on updating your app, please visit our updated API Documentation Page: V3 API - Update Your Applications to Use the New Authorization Service https://v3.developer.constantcontact.com/api_guide/auth_update_apps.html Please have a look and let us know if you have any other questions! You can reply here, or follow up with us securely via email at webservice@constantcontact.com.

John__B · ‎12-15-2021

Hello Chris, Thank you for reaching out to Constant Contact API Developer Support. My team is here to assist outside software developers with questions about building into Constant Contact's API. It looks like we've already followed up with you directly via email, but here is the information provided for visibility on the forum: If you are continuously receiving response code 429, that would indicate that your application has exceeded the daily rate limit available for your key. The standard rate limit per V3 key is 10,000 requests per day and 4 requests per second. The rate limit is reset the following day. https://developer.constantcontact.com/api_guide/rate_limits.html Please have a look and let us know if you have any other questions! Regards,

Courtney_E · ‎11-15-2021

Hello Chris , Thank you for reaching out to Constant Contact API Developer Support. My team is here to assist outside software developers with questions about building into Constant Contact's API. To remove all list memberships from a contact using the V3 API, you would want to use PUT /contacts/{contact_id} with a blank list value. PUT (update) a Contact https://v3.developer.constantcontact.com/api_reference/index.html#!/Contacts/putContact Below is an example of what that might look like. Notice that the "list_memberships" parameter is included, but left blank so that it will overwrite any existing list data: Request URL: PUT https://api.cc.email/v3/contacts/{contact_id} Request Body: { "email_address": { "address": "test@example.com", "permission_to_send": "implicit" }, "create_source": "Account", "update_source": "Account", "list_memberships": [] } Please have a look and let us know if you have any other questions!

ChrisC37 · ‎10-27-2020

As a follow up to this post, I've been able to determine that one is not supposed to encode the access token in the ("Authorization", Bearer = Access_Token) header line. Still, that leaves me stuck on the 403 error message. I've tried including the "&Scope=contact_data" in the initial oAuth2 url request but it seems to make no difference. A little insight from you folks would be amazing.

ChrisC37 · ‎08-25-2020

Thank you for your reply: So I'm a little confused. On the oAuth 2.0 Client Flow: Since the Client_id (API Key) and Secret key belong to my registered application, how does my application know who's Constant Contact account it's logging into? My application is installed at many different locations for different customers with different Constant Contact accounts. Previously, with API V1.0 we would use the account's login name and password. There is nothing that I'm sending that is unique to a specific Constant Contact Account. Please keep in mind that this is a Winforms application. Not a web app. There are no web pages involved. I issue a request in code and receive a response. What dark magic are you using to where my app knows who's Constant Contact account it's attempting to access? Thanks. Chris

Jimmy_D · ‎08-24-2020

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.

Re: Updates to API 3.0?

Re: quota_exceeded

Re: Remove List Assignment - API-3

Re: API v3.0 Access in a Visual Studio application...

Re: oAuth 2.0 and API V3.0 general questions

Re: Authorization Request - Internal Error