HTTP 401 UnauthorizedException

[KenJ32]

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.  

https://api.cc.email/v3/contacts?status=unsubscribed&include=custom_fields&limit=500&include_count=f...}

GET /v3/contacts

cache-control: no-cache

Postman-Token: #############

Authorization: Bearer {TOKEN}

User-Agent: PostmanRuntime/7.6.0

Accept: */*

Host: api.cc.email

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=

Access-Control-Allow-Methods: GET,POST,PUT,DELETE,PATCH,OPTIONS

X-Cache: Error from cloudfront

Via: 1.1 c8b22b813bc9140f3fc38a5e2fae3685.cloudfront.net (CloudFront)

X-Amz-Cf-Id: cHKfG_lKisca1yQyh9cC8WfCxERTX1sE5CzwwRo-9J56jRDA__dCNw==

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

[RJF]

I'm getting the same thing.

Even when I go to the API Reference and connect via oAuth (https://v3.developer.constantcontact.com/api_reference/index.html#!/Contacts/getContacts)
I still get the same unauthorized 401

Anyone know what would cause this to happen?

[AIMInstitute]

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.

[ScottR]

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"}

[Jimmy_D]

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.