About user942713

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

Hey Jimmy,   I have similar problems in my system, but I understand that CC is changing the refresh token each time due to a secuirity measure. But I have a question here, let's say there are multiple places in app where CC integration is required with the same account. If my users authenticate for multiple places, only one of them would work because only 1 pair of access/refresh tokens will be valid. I can still work around this problem by storing one pair of access/refresh token in one place, and using that in all places in app. BUT, tell me this, let's say 9 o clock, the acess token is going to expire. And 9:01, 3-4 places in my code pick up the refresh token to generate new access token, and then make some API call to push data in CC. Some of those requests will fail, right? Because one of them will generate a new refresh token and if the other requests are running parellel, they will pick up the old refresh token from the db in that few 100 ms, and they would fail, rigth? ... 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