cancel
Showing results for 
Search instead for 
Did you mean: 

Issue with Access/Refresh tokens

Occasional Participant

Issue with Access/Refresh tokens

So, I've been successfully using the API since September using Java/okhttp3.

 

Since yesterday, I've been having issues.  When I refresh the tokens I get a 200 response with the tokens but when I immediately use the token's provided, I get a 401 right after.  Turns out to be a nasty loop.

 

Has anyone else experienced this?

 

Best!

Larry

4 REPLIES 4
Occasional Participant

Re: Issue with Access/Refresh tokens

I was just about to create a post about this.

 

We have been using the v3 API since some weeks ago and all of sudden it stopped working.

 

We have investigating our code and came to the conclusion the issue is in the API side.

 

We can successfully make the authorization code request and receive the code.

 

Then we are able to exchange the code for an access token.

 

We are also able to use the refresh token in order to get a new access/refresh token.

 

The problem is that when we use the access_token to perform API requests, like:

 

curl -X GET \
'https://api.cc.email/v3/contacts?status=all&email=someperson%40domain.com&include_count=false&includ...' \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer INSERT_SOME_VALID_RECENT_ACCESS_TOKEN_HERE' \
-H 'Cache-Control: no-cache' \
-H 'Accept: application/json'

 

We always get the response:

 

{"error_key":"unauthorized","error_message":"Unauthorized"}

Occasional Contributor

Re: Issue with Access/Refresh tokens

I just posted the same issue in the 401 error forum.  I have been having the same issue since yesterday.  API calls were working for several days, and now I can refresh the Access Token but get a 401 error x-amzn-ErrorType: UnauthorizedException.

Occasional Participant

Re: Issue with Access/Refresh tokens

Ugh.  Thanks for letting me know about that forum.  I didn't see it.  I'll post there, too.

Moderator

Re: Issue with Access/Refresh tokens

Hello Everyone,

 

Sorry for the delayed response. As I'm sure you are already aware this issue has been resolved. We had a temporary issue with some certificates and they have been updated. Please let us know if you still see this problem.


Regards,
Jimmy D.
Tier II API Support Engineer