Urgent: LoasAuthenticationError.CLIENT_NOT_AUTHORIZED (we have standard access token)

239 views
Skip to first unread message

AdWordsApiUser

unread,
Apr 25, 2016, 2:42:07 PM4/25/16
to AdWords API Forum
We're getting LoasAuthenticationError.CLIENT_NOT_AUTHORIZED for most request for the past 15 minutes or so. We are not a new user, we have standard access. Is this being looked at? Do we need to do anything?

Mark Rogoyski

unread,
Apr 25, 2016, 2:43:33 PM4/25/16
to AdWords API Forum
We are seeing the same thing.

Gigel Chiazna

unread,
Apr 25, 2016, 3:02:42 PM4/25/16
to AdWords API Forum
yep, me too; only for some reports, not for all operations

HK

unread,
Apr 25, 2016, 3:03:36 PM4/25/16
to AdWords API Forum
We have the same issue and it will quickly become critical. We are seeing it with reports only. Our other APIs for getting campaigns, budgets, etc. are working fine, just not downloading reports.

Hans

Mark Rogoyski

unread,
Apr 25, 2016, 3:09:02 PM4/25/16
to AdWords API Forum
We are experiencing the same thing. Services like ManagedCustomerService, CampaignService, ConstantDataService, etc. all seem to work, but ReportDefinitionService seems to fail with the LoasAuthenticationError.CLIENT_NOT_AUTHORIZED error on every request.

Matt Linscott

unread,
Apr 25, 2016, 3:10:52 PM4/25/16
to AdWords API Forum
Same error here. We are getting it on the CAMPAIGN_PERFORMANCE_REPORT, CAMPAIGN_PLATFORM_TARGET_REPORT and AD_PERFORMANCE_REPORT reports. We are using the v201603 API.

Here's an example from the report log, with our auth info *'d out.

[Apr 25 2016 11:59:55.000000 - ERROR] POST /api/adwords/reportdownload/v201603 HTTP/1.1
User-Agent: curl, gzip
Accept: */*
Accept-Encoding: gzip
Authorization: Bearer **************************************************************
developerToken: ***************
clientCustomerId: **********
skipReportHeader: true
skipReportSummary: true
includeZeroImpressions: true
Content-Length: 512
Expect: 100-continue
Content-Type: multipart/form-data; boundary=----------------------------2b73dfc263ea

Parameters:
__rdquery:             SELECT
                ExternalCustomerId
            ,   CampaignId
            ,   BidModifier
            FROM CAMPAIGN_PLATFORM_TARGET_REPORT
            WHERE CampaignStatus IN [ENABLED, PAUSED]
            AND Id = 30001
            DURING TODAY
__fmt: GZIPPED_CSV

Response Code: 400
Error Message: Report download failed. Underlying errors are 
Type = 'LoasAuthenticationError.CLIENT_NOT_AUTHORIZED', Trigger = '<null>', FieldPath = ''.

On Monday, April 25, 2016 at 11:42:07 AM UTC-7, AdWordsApiUser wrote:

Mark Rogoyski

unread,
Apr 25, 2016, 3:12:18 PM4/25/16
to AdWords API Forum
We are on API v201601 and getting the same error responses.

Anthony Madrigal

unread,
Apr 25, 2016, 3:13:50 PM4/25/16
to AdWords API Forum
Hi guys,

We are currently investigating this issue. There should be an update very soon. Thanks for your patience. 

Regards,
Anthony
AdWords API Team

oli...@dashthis.com

unread,
Apr 25, 2016, 3:21:15 PM4/25/16
to AdWords API Forum
We're getting the same error here, too. No changes on our side, just regular calls.

Tiana S.

unread,
Apr 25, 2016, 3:22:42 PM4/25/16
to AdWords API Forum
Hi Anthony,

Thanks for the heads up!
Having the same issue here, on API v201509

Umesh Dengale

unread,
Apr 25, 2016, 4:10:56 PM4/25/16
to AdWords API Forum
Hello,

The engineering team has identified the issue and fix is deployed. Please try to run the reports and let us know if you experience the same issue.


Thanks,
Umesh, AdWords API Team.

Mark Rogoyski

unread,
Apr 25, 2016, 4:12:25 PM4/25/16
to AdWords API Forum
Reports seem to be working normally now. Thank you for quickly troubleshooting the issue and resolving it.

Will a postmortem be posted to explain the outage?

Joe G

unread,
Apr 25, 2016, 4:15:01 PM4/25/16
to AdWords API Forum
Seeing this error as well with v201509. Some requests go through but the majority give CLIENT_NOT_AUTHORIZED.

Tiana S.

unread,
Apr 25, 2016, 4:29:41 PM4/25/16
to AdWords API Forum
Hi Umesh,

Have been running some reports, but no longer seeing the error.
Will keep an eye out for new occurrences!

Thank you very much for the quick response on this issue and the quick resolution.
Very curious as to what was the cause of this. As Mark mentioned, I would also love to see a postmortem to explain the outage!

Thanks again,

Tiana

Josh Radcliff (AdWords API Team)

unread,
Apr 25, 2016, 5:30:11 PM4/25/16
to AdWords API Forum
Hi Tiana,

This was due to an internal issue with the report servers, so there wasn't any action you could take in this situation aside from notifying us of the problem.

Thanks,
Josh, AdWords API Team
Reply all
Reply to author
Forward
0 new messages