MCC Test Account returning QuotaCheckError.ACCOUNT_INACTIVE on API Call

[AdManager Reweb]

We have created a test account to begin the API tests. However, when we try to get the campaigns, the message : QuotaCheckError.ACCOUNT_INACTIVE is returned from SOAP.

The DeveloperToken is still peding, but this should not be a problem, right?

Our DeveloperToken is b9ymIsVGVEYnOkHFx84WbA and our ClientID is 750758403885.apps.googleusercontent.com .

Thank you!

[Anash P. Oommen (AdWords API Team)]

Hi,

Yes, that shouldn't happen as far as I can tell. A test account is closed and hence should be inactive, but you shouldn't get that error message back. Could you post a sanitized SOAP message so I can take a look?

Cheers,
Anash P. Oommen,

AdWords API Advisor

[tes...@nirandas.com]

Me too facing same issue. Generally ACCOUNT_INACTIVE comes when billing information is not set, but I've set billing info on both MCC test account and the child account. I've tried unlinking and linking them back again. My test mcc account is not yet approved.

here is my soap request.

[Aug 29 2013 11:07:37.000000 - ERROR] POST /api/adwords/cm/v201306/CampaignService?access_token=ya29.*****************4Lf0d*******RTeg************ZRgjvz0rz HTTP/1.1
Host: adwords.google.com
Connection: Keep-Alive
User-Agent: PHP-SOAP/5.4.14, gzip
Accept-Encoding: gzip, deflate
Content-Encoding: gzip
Content-Type: text/xml; charset=utf-8
SOAPAction: ""
Content-Length: 521

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="https://adwords.google.com/api/adwords/cm/v201306">
  <SOAP-ENV:Header>
    <ns1:RequestHeader>
      <ns1:clientCustomerId>511-***-6051</ns1:clientCustomerId>
      <ns1:developerToken>tl7******sjZzY******s3iA</ns1:developerToken>
      <ns1:userAgent>th****th sy***ms (AwApi-PHP/4.5.1, Common-PHP/5.0.0, PHP/5.4.14)</ns1:userAgent>
    </ns1:RequestHeader>
  </SOAP-ENV:Header>
  <SOAP-ENV:Body>
    <ns1:get>
      <ns1:serviceSelector>
        <ns1:fields>Id</ns1:fields>
        <ns1:fields>Name</ns1:fields>
        <ns1:fields>Impressions</ns1:fields>
        <ns1:fields>Clicks</ns1:fields>
        <ns1:fields>Cost</ns1:fields>
        <ns1:fields>Ctr</ns1:fields>
        <ns1:predicates>
          <ns1:field>Impressions</ns1:field>
          <ns1:operator>GREATER_THAN</ns1:operator>
          <ns1:values>0</ns1:values>
        </ns1:predicates>
        <ns1:dateRange>
          <ns1:min>20130822</ns1:min>
          <ns1:max>20130828</ns1:max>
        </ns1:dateRange>
        <ns1:paging>
          <ns1:startIndex>0</ns1:startIndex>
          <ns1:numberResults>500</ns1:numberResults>
        </ns1:paging>
      </ns1:serviceSelector>
    </ns1:get>
  </SOAP-ENV:Body>
</SOAP-ENV:Envelope>


AND THE RESPONSE

HTTP/1.1 500 Internal Server Error
Content-Type: text/xml; charset=UTF-8
Content-Encoding: gzip
Date: Thu, 29 Aug 2013 05:37:47 GMT
Expires: Thu, 29 Aug 2013 05:37:47 GMT
Cache-Control: private, max-age=0
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
Content-Length: 503
Server: GSE

<?xml version="1.0"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Header>
    <ResponseHeader xmlns="https://adwords.google.com/api/adwords/cm/v201306">
      <requestId>0004e50f818771500a422541000031df</requestId>
      <serviceName>CampaignService</serviceName>
      <methodName>get</methodName>
      <operations>0</operations>
      <responseTime>49</responseTime>
    </ResponseHeader>
  </soap:Header>
  <soap:Body>
    <soap:Fault>
      <faultcode>soap:Server</faultcode>
      <faultstring>[QuotaCheckError.ACCOUNT_INACTIVE @ ; trigger:'&lt;null&gt;']</faultstring>
      <detail>
        <ApiExceptionFault xmlns="https://adwords.google.com/api/adwords/cm/v201306">
          <message>[QuotaCheckError.ACCOUNT_INACTIVE @ ; trigger:'&lt;null&gt;']</message>
          <ApplicationException.Type>ApiException</ApplicationException.Type>
          <errors xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="QuotaCheckError">
            <fieldPath/>
            <trigger>&lt;null&gt;</trigger>
            <errorString>QuotaCheckError.ACCOUNT_INACTIVE</errorString>
            <ApiError.Type>QuotaCheckError</ApiError.Type>
            <reason>ACCOUNT_INACTIVE</reason>
          </errors>
        </ApiExceptionFault>
      </detail>
    </soap:Fault>
  </soap:Body>
</soap:Envelope>

[PinYun Peng]

I have the same problem.

Application Client ID: 188261182067-vjueniqmj56m5630nggcurqv1crejahd.apps.googleusercontent.com Test Account MCM ID: 156-754-4053

The attach file is soap_xml.log of failed API Call. 

( The access_token and developerToken are replaced by random text. If they are necessary, I can re-attach.)

On Wednesday, August 28, 2013 4:59:07 PM UTC+8, Anash P. Oommen (AdWords API Team) wrote:

[Anash P. Oommen (AdWords API Team)]

Hi,

Looks like the error happens because your developer token is in a test MCC account, we don't support that configuration. Test MCCs are meant to test ManagedCustomerService related calls or to manage a hierarchy of test Adverttiser accounts. 

Please use your production developer token and test MCC credentials to make calls to test account. If you don't have a production developer token, you should sign up for one from a non-test MCC account.

We will update the documentation to make this more clear.

Cheers,

Anash P. Oommen,

AdWords API Advisor.

[Ludo Fulop]

This is crazy... 

do i understand well, that i can not use test account to build my application (or at least features that i need), but i need to send you parts/screenshots of the application (or it's non existing functionality - as i can not develop it) for non-test developer token approval?

Or am i missing something?

Thanks,

Ludo

Dňa štvrtok, 29. augusta 2013 10:29:02 UTC+2 Anash P. Oommen (AdWords API Team) napísal(-a):

[rob.l...@mac.com]

So is it correct that I can't develop against a MCC test account??  I have to have a production account, which I can't get because I have nothing to show for an application yet???   Currently I'm just running the example php scripts to familiarise my self with the api before we start the design work of a new application.

Can someone please advise

Thanks

Rob

[Danial Klimkin]

Hello Rob,

You can develop against MCC test account but you need to use a token from a production account. This token does not need to be approved though, so you can request one and use it right away.

-Danial, AdWords API Team.

[kano patel]

i also have same problem
its must necessary to used production mcc developer's token to call api???????????????

On Tuesday, August 27, 2013 7:07:22 PM UTC+5:30, AdManager Reweb wrote:

[Anash P. Oommen (AdWords API Team)]

Hi Kano,

Yes, it is necessary to have a production developer token to make calls to a test account. Though, it is not as hard as it might sound. Just signup for a regular developer token from your MCC if you haven't done so yet. Make sure you enter your credit card details so that the token is activated and AdWords API Terms and Conditions are accepted. Now use this token to make calls to the test account. It doesn't matter if your token is still under review, you should be able to make calls to AdWords test accounts and develop your software. If you don't have your software built yet, the token review team may accept screen mockups and writeup of the control flow instead. Respond to the email that you got from the review team when you signed up for AdWords API and ask them if you could provide screen mockups instead of completed application and screenshots. They will guide you through the review process.

Cheers,
Anash P. Oommen,
AdWords API Advisor.

[GigiCom]

Hi,

i read all Posts and check my account but every time I try to GetCampaigns or AddCampaigns from AdWord Library i get the Issue 'INCOPLETE SIGNUP'

any Idea?

 Thank You

[Anash P. Oommen (AdWords API Team)]

Hi,

You need to enter you billing details, and accept AdWords API T&C to be able to use the developer token. If you are making calls to your production account, you also need to get the token approved. This is not required when making calls to test accounts.

Cheers,
Anash P. Oommen
AdWords API Advisor.

[adwor...@trackingsoft.com]

we are in the similar situation - we didn't complete the billing and T&Cs, but now I can't find where I should enter my billing info - there is no billing link within adwords account. There is "billign summary", but no place to enter billing and accept T&C.