About raleighb3

Hello SeyiK9,   Thank you for reaching out to Constant Contact API Developer Support.    When using the new OAuth2 flows that are available for V3 using our recently implemented authorization management service, the access token lifetime is now a static 24 hours, and you have the option of using rotating refresh tokens or long lived refresh tokens:   Rotating Refresh Tokens will not expire unless they have been used and/or a new token set has been generated. Rotating refresh tokens can only be used once, as generating a new set of tokens causes all previous refresh tokens to expire.    Once you have your first set of tokens, you’ll want to set both the access token and the refresh token as values for corresponding variables in your application, so that when your program requests a new set of tokens it can assign new values to both of those variables to maintain an authenticated connection.   Long Lived Refresh Tokens (which can be configured within your V3 key’s settings), allow you to use the same refresh token continuously to generate new Access Tokens. You can use the same configuration as you would for the rotating refresh tokens if desired, you’ll just get back the same refresh token value each time when receiving your new access token.   Update Your Applications to Use the New Authorization Service https://v3.developer.constantcontact.com/api_guide/auth_update_apps.html   While we generally recommend using rotating refresh tokens (as they're more secure), using a long lived refresh token should alleviate many of the situations that we've seen reported where a refresh token becomes invalid, and then requires a new authorization request.   Currently, the Long Lived Refresh Tokens are only compatible with our OAuth2 Authorization Code Flow, and must be used at least once every 180 days in order to remain valid.   OAuth2 Authorization Code Flow https://v3.developer.constantcontact.com/api_guide/server_flow.html   Please have a look and let us know if you have any other questions! ... View more

Hello @user942713,   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.   When it comes to Access Tokens they do expire/overwrite after a certain amount of time or when a user generates a new Access Token depending on which API version they're using. This was implemented as a security measure, if you need multiple Access Tokens on an account for our V2 API the only workaround at this time would be to have multiple users on the account that way they can all have a separate Access Tokens. Our V3 API on the other hand does not offer static Access Tokens as they expire every 2 hours. Just in case, below are links to documentation on Access Tokens for both our V3 and V2 APIs.   V3 API (Expires) https://v3.developer.constantcontact.com/api_guide/client_flow.html#step-3-retrieve-the-access-token   V2 API (Overwrites) https://v2.developer.constantcontact.com/docs/authentication/authentication.html   Please reply directly to this post if you have any other questions!   Regards, ... View more

In my case, I had 2 desktop pc's.   On each PC, my same User had to go through the Authorization process.  In my case, I used the Server flow.  So, this same CC User has now granted Authority on 2 PC's.  The initial Access/Refresh token values on the PCs were not the same.  And in using the token values on either PC, I never encountered any error.     That is how I made my determination.   Though this has not been confirmed by anyone at CC.    If this is not currently the case, then perhaps CC has modified its end of things. ... View more

Not so obvious 🙂 Yes, that was the problem.  I wasn't aware of the short life of the Auth Code.    Thanks! ... View more

Yes.  The RefreshToken is what you use as it lives forever ... or so it seems.  Simply be sure to ask for and store the new RefreshToken for use next time. ... 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

  ...Authorization' => 'Bearer {$access_oken}'... ... View more

Hi @RicK22,   As @raleighb3 mentioned either your Access Token does not have the correct scopes required, or the account does not have the correct permissions to create an email campaign. ... View more

Thanks!  That did the trick. ... View more

I will start a new thread if you'd like.  Just let me know.   But my issue is the very same as in the original post.  This is also a Windows application, using a webBrowser control.   Doing the 'server' flow.  When "Allow" is clicked, it appears that nothing is getting triggered. Browser remains on the Allow/Deny page.   From log---> WebBrowser1_Navigated https://idfed.constantcontact.com/as/jkr4A9muH2/resume/as/authorization.ping?resume=/as/jkr4A9muH2/resume/as/authorization.ping&spentity=null&scope=contact_data WebBrowser1_DocumentCompleted https://idfed.constantcontact.com/as/jkr4A9muH2/resume/as/authorization.ping?resume=/as/jkr4A9muH2/resume/as/authorization.ping&spentity=null&scope=contact_data WebBrowser1_Navigating https://idfed.constantcontact.com/as/jkr4A9muH2/resume/as/authorization.ping WebBrowser1_Navigating javascript:void(0) WebBrowser1_Navigating https://idfed.constantcontact.com/as/jkr4A9muH2/resume/as/authorization.ping WebBrowser1_Navigating javascript:void(0)   ... View more