Hi Mike, Cool. For future reference, it is useful to look at the raw HTTP messages to figure out what might be wrong with the request. Fiddler2 is a good HTTPs proxy for debugging. See https://github.com/googleads/googleads-adwords-dotnet-lib/wiki/How-to-capture-SOAP-messages for some relevant configuration details.
Also, I'd recommend the .NET client library<https://github.com/googleads/googleads-adwords-dotnet-lib>if you were to consider campaign management as well. As noted in the NoClientLibrary wiki, making calls using Visual Studio stubs is not that easy with AdWords API stub. Cheers, Anash P. Oommen, AdWords API Advisor. On Monday, March 3, 2014 5:27:20 PM UTC-5, Mike Sullivan wrote: > > Never mind...my developer token wasn't completely enabled due to a > technical glitch. All is well now. > > > On Sunday, March 2, 2014 10:06:01 AM UTC-5, Mike Sullivan wrote: >> >> Knowledgeable, but newbie with the AdWords API. Can't get the first query >> to work, and have tried everything....I think. Would love any insight... >> >> I have tried my custom code, using the referenced .NET library, as well >> as a snippet of NoClientLibrary from here: >> https://code.google.com/p/google-api-adwords-dotnet/wiki/NoClientLibrary >> >> All produce the same result: "The remote server returned an error: (400) >> Bad Request." >> Header: { >> X-Content-Type-Options: nosniff >> X-Frame-Options: SAMEORIGIN >> X-XSS-Protection: 1; mode=block >> Transfer-Encoding: chunked >> Cache-Control: private, max-age=0 >> Content-Type: text/xml >> Date: Fri, 28 Feb 2014 16:43:29 GMT >> Expires: Fri, 28 Feb 2014 16:43:29 GMT >> Server: GSE >> } >> >> My header and query looks like: >> https://adwords.google.com//api/adwords/reportdownload/v201309 >> { >> User-Agent: _something_ >> Authorization: Bearer _validOauthAccessToken_ >> clientCustomerId: XXX-XXX-XXXX >> developerToken: _myDeveloperToken_ >> returnMoneyInMicros: true >> Content-Type: application/x-www-form-urlencoded >> } >> >> {__rdquery=SELECT+AccountId%2CAccountDescriptiveName+FROM+ACCOUNT_PERFORMANCE_REPORT+DURING+LAST_30_DAYS&__fmt=XML} >> >> >> I have tried several queries, using various reports and fields straight >> out of the docs. Everything comes back with the 400 error. >> >> >> I also tried messing with the developer token and Oauth otken and got the >> same result??? I would have expected an authorization failure, which makes >> me think I have overlooked something big up front. >> >> Help..... >> > -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 --- You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
