Re: New error only in mutate AdwordsUserListService calls: QuotaCheckError.INVALID_TOKEN_HEADER @

[Sreelakshmi Sasidharan (AdWords API Team)]

Hi, 

I deleted your original post as it contains your confidential information such as your access token. In the future, please do not include any private information in a public post. You can refer to this guide before posting. Re-posting this with masked information:

"I've a suite test, performing some basic test every day to adwords api, using soap calls. 

Today I saw a regression in call:

URL: https://adwords.google.com/api/adwords/rm/v201802/AdwordsUserListService

Headers: {headers={Authorization=REDACTED}, connect_timeout=60000, method=POST, content_type=application/soap+xml; charset=UTF-8, read_timeout=60000, content_length=1315}

Postbody:

<?xml version="1.0"?>

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

 <soapenv:Header>

   <ns1:RequestHeader xmlns:ns1="https://adwords.google.com/api/adwords/rm/v201802" soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next" soapenv:mustUnderstand="0">

     <ns1:clientCustomerId>******</ns1:clientCustomerId>

     <ns1:developerToken>xxxxxxxx</ns1:developerToken>

     <ns1:userAgent>MagNews Google Match Connector</ns1:userAgent>

     <ns1:validateOnly>false</ns1:validateOnly>

     <ns1:partialFailure>false</ns1:partialFailure>

   </ns1:RequestHeader>

 </soapenv:Header>

 <soapenv:Body>

   <mutate xmlns="https://adwords.google.com/api/adwords/rm/v201802"><operations><ns10:operator xmlns:ns10="https://adwords.google.com/api/adwords/cm/v201802">ADD</ns10:operator><ns11:operand xsi:type="ns11:CrmBasedUserList" xmlns:ns11="https://adwords.google.com/api/adwords/rm/v201802"><ns11:name>nome #1523345583377</ns11:name><ns11:description>descrizione</ns11:description><ns11:membershipLifeSpan>15</ns11:membershipLifeSpan><ns11:uploadKeyType>CONTACT_INFO</ns11:uploadKeyType></ns11:operand></operations></mutate>

 </soapenv:Body>

</soapenv:Envelope>

That's the error:

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

<soap:Header>

  <ns2:ResponseHeader xmlns:ns2="https://adwords.google.com/api/adwords/rm/v201802" xmlns="https://adwords.google.com/api/adwords/cm/v201802">

  <requestId>0005697988642cb80a8135c5c203179f</requestId>

  <serviceName>AdwordsUserListService</serviceName>

  <methodName>mutate</methodName>

  <operations>1</operations>

  <responseTime>52</responseTime>

  </ns2:ResponseHeader>

</soap:Header>

<soap:Body><soap:Fault>

 <faultcode>soap:Client</faultcode>

     <faultstring>[QuotaCheckError.INVALID_TOKEN_HEADER @ ]</faultstring>

   <detail>

       <ns2:ApiExceptionFault xmlns="https://adwords.google.com/api/adwords/cm/v201802" xmlns:ns2="https://adwords.google.com/api/adwords/rm/v201802">

<message>[QuotaCheckError.INVALID_TOKEN_HEADER @ ]</message>

   <ApplicationException.Type>ApiException</ApplicationException.Type>

    <errors xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="QuotaCheckError">

      <fieldPath></fieldPath>

<trigger></trigger>

    <errorString>QuotaCheckError.INVALID_TOKEN_HEADER</errorString>

<ApiError.Type>QuotaCheckError</ApiError.Type>

 <reason>INVALID_TOKEN_HEADER</reason>

  </errors></ns2:ApiExceptionFault>

      </detail></soap:Fault>

</soap:Body>

</soap:Envelope>

I searched this error on the net and it's seems that the developer token should be wrong.... the strange thing is that this test was successfully running yesterday, and nobody is modifying the code at least from one month!!

The other strange thing is that I have another test using getCustomers endopoint with the same developer token and it doesn't fail!!

URL: https://adwords.google.com/api/adwords/mcm/v201802/CustomerService

Headers: {headers={Authorization=REDACTED}, connect_timeout=60000, method=POST, content_type=application/soap+xml; charset=UTF-8, read_timeout=60000, content_length=886}

Postbody:

<?xml version="1.0"?>

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

 <soapenv:Header>

   <ns1:RequestHeader xmlns:ns1="https://adwords.google.com/api/adwords/mcm/v201802" soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next" soapenv:mustUnderstand="0">

     <ns1:clientCustomerId>*******</ns1:clientCustomerId>

     <ns1:developerToken>xxxxxxxx</ns1:developerToken>

     <ns1:userAgent>MagNews Google Match Connector</ns1:userAgent>

     <ns1:validateOnly>false</ns1:validateOnly>

     <ns1:partialFailure>false</ns1:partialFailure>

   </ns1:RequestHeader>

 </soapenv:Header>

 <soapenv:Body>

   <getCustomers xmlns="https://adwords.google.com/api/adwords/mcm/v201802"></getCustomers>

 </soapenv:Body>

</soapenv:Envelope>

oap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Header><ResponseHeader xmlns:ns2="https://adwords.google.com/api/adwords/cm/v201802" xmlns="https://adwords.google.com/api/adwords/mcm/v201802"><ns2:requestId>00056979961228880a1b1994ad07058f</ns2:requestId><ns2:serviceName>CustomerService</ns2:serviceName><ns2:methodName>getCustomers</ns2:methodName><ns2:operations>0</ns2:operations><ns2:responseTime>178</ns2:responseTime></ResponseHeader></soap:Header><soap:Body><getCustomersResponse xmlns="https://adwords.google.com/api/adwords/mcm/v201802" xmlns:ns2="https://adwords.google.com/api/adwords/cm/v201802"><rval><customerId>3854692876</customerId><currencyCode>EUR</currencyCode><dateTimeZone>Europe/Rome</dateTimeZone><descriptiveName>JUnit Test (DON'T TOUCH)</descriptiveName><canManageClients>false</canManageClients><testAccount>true</testAccount><autoTaggingEnabled>false</autoTaggingEnabled><parallelTrackingEnabled>false</parallelTrackingEnabled><conversionTrackingSettings><effectiveConversionTrackingId>0</effectiveConversionTrackingId><usesCrossAccountConversionTracking>false</usesCrossAccountConversionTracking><optimizeOnEstimatedConversions>false</optimizeOnEstimatedConversions></conversionTrackingSettings><remarketingSettings><snippet>&lt;!-- Google Code for Remarketing Tag --&gt;

&lt;!--------------------------------------------------

Remarketing tags may not be associated with personally identifiable information or placed on pages related to sensitive categories. See more information and instructions on how to setup the tag on: http://google.com/ads/remarketingsetup

---------------------------------------------------&gt;

&lt;script type="text/javascript"&gt;

/* &lt;![CDATA[ */

var google_conversion_id = 812226326;

var google_custom_params = window.google_tag_params;

var google_remarketing_only = true;

/* ]]&gt; */

&lt;/script&gt;

&lt;script type="text/javascript" src="//www.googleadservices.com/pagead/conversion.js"&gt;

&lt;/script&gt;

&lt;noscript&gt;

&lt;div style="display:inline;"&gt;

&lt;img height="1" width="1" style="border-style:none;" alt="" src="//googleads.g.doubleclick.net/pagead/viewthroughconversion/812226326/?guid=ON&amp;amp;script=0"/&gt;

&lt;/div&gt;

&lt;/noscript&gt;

</snippet><googleGlobalSiteTag>&lt;!-- Global site tag (gtag.js) - Google AdWords: 812226326 --&gt;

&lt;script async src="https://www.googletagmanager.com/gtag/js?id=AW-812226326"&gt;&lt;/script&gt;

&lt;script&gt;

 window.dataLayer = window.dataLayer || [];

 function gtag(){dataLayer.push(arguments);}

 gtag('js', new Date());

  gtag('config', 'AW-812226326');

&lt;/script&gt;

</googleGlobalSiteTag></remarketingSettings></rval></getCustomersResponse></soap:Body></soap:Envelope>

Why does it happens????

Thanks,

Sreelakshmi, AdWords API Team

[Sreelakshmi Sasidharan (AdWords API Team)]

Hi, 

We are currently looking into this issue, will update you soon on what we find. 

[Sreelakshmi Sasidharan (AdWords API Team)]

Hi, 

Our team is actively working on fixing this issue. I will keep you posted on the updates.

[Sreelakshmi Sasidharan (AdWords API Team)]

Hi All,

This issue is resolved now and you are not expected to see any more failures. Please let us know if you are still encountering the INVALID_TOKEN_HEADER error.