Hi Christopher, The application token is no longer required when using the API, and new signups for the API are not given an application token. However, since you applied for an application token before this change, and your application token wasn't approved yet, and you were passing it with your request, you were getting an error. I've manually approved your token, but you can feel free to omit this token in the future.
Best, - Eric On Mar 5, 1:46 pm, Dhammiko <[email protected]> wrote: > Eric, > > Thanks for replying. Here is the entirety of the SOAP response, > I'm not seeing a requestID in it. I downloaded the perl code I'm > using to access your API directly from the repository and replaced the > variables with my login name and password, developer token and > application token. I changed it from 'sandbox' to 'adwords' as > well. Here is the response: > > SOAP::Transport::HTTP::Client::send_receive: HTTP/1.1 500 Internal > Server Error > Cache-Control: private, max-age=0 > Connection: close > Date: Fri, 05 Mar 2010 18:43:51 GMT > Server: GSE > Content-Type: text/xml; charset=utf-8 > Expires: Fri, 05 Mar 2010 18:43:51 GMT > Client-Date: Fri, 05 Mar 2010 18:43:51 GMT > Client-Peer: 72.14.204.112:443 > Client-Response-Num: 1 > Client-SSL-Cert-Issuer: /C=US/O=Google Inc/CN=Google Internet > Authority > Client-SSL-Cert-Subject: /C=US/ST=California/L=Mountain View/O=Google > Inc/CN=adwords.google.com > Client-SSL-Cipher: AES256-SHA > Client-SSL-Warning: Peer certificate not verified > Client-Transfer-Encoding: chunked > X-Content-Type-Options: nosniff > X-Frame-Options: SAMEORIGIN > X-XSS-Protection: 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:Body> > <soapenv:Fault> > <faultcode>soapenv:Server.userException</faultcode> > <faultstring>Application information pending.</faultstring> > <detail> > <ns1:fault xmlns:ns1="https://adwords.google.com/api/adwords/v13";> > <ns1:code>129</ns1:code> > <ns1:message>Application information pending.</ns1:message> > </ns1:fault> > </detail> > </soapenv:Fault> > </soapenv:Body> > </soapenv:Envelope> > > On Mar 4, 10:12 am, AdWords API Advisor <[email protected]> > wrote: > > > > > Hi Christopher, > > > Do you have the requestId for a request that demonstrates this > > behavior? I can use that to look up further information about your > > account. > > > Best, > > - Eric > > > On Mar 3, 1:23 pm, Dhammiko <[email protected]> wrote: > > > > Hello all, I have a question about my API developer key. > > > > When I log into the adwords MCC my developer token has a green 'Valid' > > > tag next to it. > > > > I downloaded some perl API code from the adwords repository and > > > configured it with my MCC login and password and keys. > > > > This is the API error message when running it: > > > > The following SOAP fault occurred: > > > faultcode: soapenv:Server.userException > > > faultstring: Application information pending. > > > > I tried going into the MCC and resetting my key which worked but the > > > new key, while also Valid gives me the same error code. > > > > It's not working on 'sandbox' or on 'adwords'. Any advice is > > > appreciated. > > > > -Christopher -- You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en.
