Re: newbie - my first ad hoc report request - getting a 400 response

Big thanks to everybody who tried to help me. It eventually proved to be a machine specific problem. If I run it on another PC, it works fine. I've been having some Java problems recently on my main machine, and that's my best guess as to why it wasn't working. Anyway, thanks all, Keith -- --

Re: newbie - my first ad hoc report request - getting a 400 response

Keith, That is unlikely. A 400 error suggests the request is bad. A 403 would be expected for a permissions issue. AdHoc report requests are read only operations also. I don't see anything obvious wrong with your request. Just on a hunch, try changing the Id field to AdGroupId which is also l

Re: newbie - my first ad hoc report request - getting a 400 response

Just in case anybody else is monitoring this thread (I'm in touch offline with Jonathan Shalz): I just recalled something that I think might be the explanation for the 400 response: the manager of the Adwords account I was using was reluctant to give my Google account full access to the API; so

Re: newbie - my first ad hoc report request - getting a 400 response

That looks pretty reasonable. Here's a successful request I just ran: POST https://adwords.google.com/api/adwords/reportdownload/v201306 HTTP/1.1 Content-Type: application/x-www-form-urlencoded Authorization: GoogleLogin auth=X clientCustomerId: 123-456-7890 developerToken: XX

Re: newbie - my first ad hoc report request - getting a 400 response

> > Jonathan >> > Thanks for the suggestion. I changed the authorization line as you indicated. I was already using the dashes in the clientCustomerId. However, I still got the same 400 response. Below is the actual request (with IDs masked). If you spot anything that looks wrong, I'd love to

Re: newbie - my first ad hoc report request - getting a 400 response

I use a slightly different format for the authorization; what you have may work in principle, too, but this is what I use (successfully): Authorization: GoogleLogin auth=XXX Also, I'm formatting the clientCustomerId with dashes, 000-000-; I don't know if that's required. If you'd like to p

Re: newbie - my first ad hoc report request - getting a 400 response

I thought I should show what Fiddler shows as the request body, with various identifying information X'd out manually, thanks: 11GUID:----5.00.7804.1000XX4371033State Message DataFull20130718201316.222000+0001.01.0XX.XX.XXX.com-2147012721P018 -- -- =

Re: newbie - my first ad hoc report request - getting a 400 response

> > Anash, I was able to get Fiddler working. In the header response panel, it > shows what's shown in the screen cap below. Not sure there's any useful > information, though. What do you suggest? Thanks, Keith >

Re: newbie - my first ad hoc report request - getting a 400 response

> > Thanks so much for your help, Anash. I'm not using a client library, so >> can't figure out how to apply the guidance on that page you linked. >> However, I'm going to just install Fiddler and see if I can figure out >> on >> my own how to get it to show the response body a

Re: newbie - my first ad hoc report request - getting a 400 response

Hi Keith, 400 error means the request is going through, but there is something wrong with the request itself. You need to read the response body (even if you get 400) to get the details of the error message. Or you can set a proxy to your HTTPS Connection, try using Fiddler2. There's a wiki ava

Re: newbie - my first ad hoc report request - getting a 400 response

Hi guys, I was advised by our Tech Support that the http request was likely not even being received properly. To quote: > An http 400 error is saying there is a problem with the REQUEST. That is > why you aren't getting a response. That ususally means you are not building > the request the wa

Re: newbie - my first ad hoc report request - getting a 400 response

> > Hi Takeshi and Anash. Apologies for the late response. It turned out I had >>> to make a long absence from work. I just tried running my code again, same >>> response. This time I added something to capture the response header. >>> Unfortunately, the software I'm using to do this seems to a