AdWords API Re: Errors not descriptive

2010-01-29 Thread Maxim
OK, I was confused, because Axis did not generate a class for SoapHeader type in Wsdl. To whom it may concern, if you are using Axis +Ant to generate Soap client for Google AdWords API, make sure you use all="true" parameter when you invoke Axis-wsdl2java Ant task. Thanks, Eric. -- You received

AdWords API Re: Errors not descriptive

2010-01-29 Thread Maxim
OK, I see it. I looked at Google's client libraries' source code to see how to set the header properly. It would help if instead of hardcoding the request header type definition inside client libraries you'd actually defined it in WSDL. MSN did just that: You could do something like that

AdWords API Re: Errors not descriptive

2010-01-29 Thread AdWords API Advisor
Hi Maxim, You are correct, the applicationToken header is no longer required. However, you still haven't built your header correctly. There should be one RequestHeader element with an element inside of it for each header value. Please look at my example again. Best, - Eric On Jan 29, 4:23 pm,

AdWords API Re: Errors not descriptive

2010-01-29 Thread Maxim
Still no luck... Same response. clientEmail header does not apply in this case. POST /api/adwords/cm/v200909/CampaignService HTTP/1.0 Content-Type: text/xml; charset=utf-8 Accept: application/soap+xml, application/dime, multipart/related, text/* User-Agent: Axis/1.4 Host: adwords.google.com Cache-

AdWords API Re: Errors not descriptive

2010-01-29 Thread Maxim
Hello. I understand one header should be "authToken", not just "auth". But the API blog says "applicationToken" is no longer required. Is that correct? -- You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to ad

AdWords API Re: Errors not descriptive

2010-01-29 Thread AdWords API Advisor
Hi Maxim, It looks like your SOAP headers aren't set correctly. The SOAP headers should look like this: https://adwords.google.com/api/adwords/cm/ v200909"> INSERT_AUTHENTICATION_TOKEN_HERE INSERT_USERAGENT_HERE INSERT_DEVELOPER_TOKEN_HERE INSERT_APPLICATION_TOKEN_

AdWords API Re: Errors not descriptive

2010-01-28 Thread Maxim
Here's a very basic API call: return campaignService.get(new CampaignSelector(new long[0], new CampaignStatus[0], null, null)).getEntries(); results in: POST /api/adwords/cm/v200909/CampaignService HTTP/1.0 Content-Type: text/xml; charset=utf-8 Accept: application/soap+xml, application/dime, mult

AdWords API Re: Errors not descriptive

2010-01-28 Thread AdWords API Advisor
Hi, This error usually indicates that the operand wasn't set on the operation, but it appears that you've done that. Do you have the associated SOAP XML request and response for that error? Best, - Eric Koleda, AdWords API Team On Jan 27, 8:42 pm, Maxim wrote: > I'm getting same error while ca

AdWords API Re: Errors not descriptive

2010-01-27 Thread Maxim
I'm getting same error while calling other methods in campaign service with v2009. On Jan 27, 3:29 pm, shriny wrote: > Errors not descriptive > > I am getting this error when trying to add campaigns using new api in > Java > > com.google.api.adwords.cm.ApiException_Exception: > [RequiredError.REQ