Showing results for 
Search instead for 
Did you mean: 
Due to an issue with YouTube, inserting videos in your emails is showing an error. Until they are able to resolve this issue, we recommend using a different video hosting service. We will continue to monitor this outage and update you as we have more information.

HTTP 401 UnauthorizedException

Occasional Contributor

HTTP 401 UnauthorizedException

For several days my CC v3 API calls were working both in Postman and in my R Script.  Yesterday the calls started failing.  I am successfully retrieving the OAUTH token, but after passing it to the final GET call, I am getting the response below.  Any assistance would be appreciated.}


GET /v3/contacts
cache-control: no-cache
Postman-Token: #############
Authorization: Bearer {TOKEN}
User-Agent: PostmanRuntime/7.6.0
Accept: */*
accept-encoding: gzip, deflate
HTTP/1.1 401
status: 401
Content-Type: application/json
Content-Length: 59
Connection: keep-alive
Date: Tue, 22 Jan 2019 16:42:31 GMT
x-amzn-RequestId: b4cb3627-1e64-11e9-b9be-5558a99d58b5
Access-Control-Allow-Origin: *
Access-Control-Allow-Headers: Content-Type,X-Amz-Date,Authorization,X-Api-Key
x-amzn-ErrorType: UnauthorizedException
x-amz-apigw-id: T6guSGURoAMFSgw=
X-Cache: Error from cloudfront
Via: 1.1 (CloudFront)
X-Amz-Cf-Id: cHKfG_lKisca1yQyh9cC8WfCxERTX1sE5CzwwRo-9J56jRDA__dCNw==
Tags (1)

Re: HTTP 401 UnauthorizedException

I'm getting the same thing.


Even when I go to the API Reference and connect via oAuth (!/Contacts/getContacts)
I still get the same unauthorized 401


Anyone know what would cause this to happen?

Occasional Participant

Re: HTTP 401 UnauthorizedException

I'm also getting a 401 immediately after a successful token refresh.  I've been using the API with no issues for several months but all of a sudden, 401 errors.  This started yesterday at 12:09 PM.


I can refresh as many times as I want, but no matter what tokens I get back, I get a 401 response.

Occasional Participant

Re: HTTP 401 UnauthorizedException

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 \
'' \
-H 'Content-Type: application/json' \
-H 'Cache-Control: no-cache' \
-H 'Accept: application/json'


We always get the response:




Re: HTTP 401 UnauthorizedException

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.

Jimmy D.
Tier II API Support Engineer
Regular Visitor

Re: HTTP 401 UnauthorizedException

I am currently experiencing this issue... 5/15/2019.


Re: HTTP 401 UnauthorizedException



The issue in the original post was due to a temporary system issue. I'm not aware of a repeat of that issue. Are you still having this problem? During the previous issue we were able to replicate using our API Tester page at!/Contacts/getContacts


If you are still having the issue, do you also see it using this API Reference tester?


Please have a look and let me know if you have any questions!


David B.
Tier II API Support Engineer


Re: HTTP 401 UnauthorizedException




I can confirm seeing the same error/issue.  We have OAuth Server Flow implemented - can receive code from our app, replace access and refresh tokens too.


When we make go to execute a curl request  in our code, we see this same error on screen.


Any suggestions would be helpful.


Thank you.


Re: HTTP 401 UnauthorizedException

Hi @DanielC171 and @ArthurB21338,


If you are receiving this error still then it would be due to an issue with the call or the data being sent as we are not currently experiencing a system issue that would cause this.


I would verify that your code is correctly retrieving the Access Token and you can make a call with a new Access Token then attempt going through the refresh flow. If the error only occurs after going through the refresh flow verify that you are correctly replacing the old Access Token with the new Access Token.


If you are still having issues it would be beneficial to see a code snippet. Generally we recommend to email us at that point (; however you are welcome to post the code here as well.

Jimmy D.
Tier II API Support Engineer