Hello everyone,

I'm working on an application that retrieves data from the Adwords API and 
I'm facing the same 400 - Bad Request problem. We are working with the 
v201710 version. 
Yesterday I worked normally on the application and today when I arrived I 
faced the exact same problem reported here. I didn't change anything in the 
code that was working just yesterday! 
I spent a lot of time searching for a possible mistake and just want to 
make sure that it might not be an error from my part.

Thanks a lot for your attention!

best regards,

Arthur

Em quarta-feira, 18 de julho de 2018 12:58:51 UTC-3, Josh Radcliff (AdWords 
API Team) escreveu:
>
> Hi Zweitze,
>
> Thanks for providing those details. The engineer investigating this said 
> they'll be quite helpful. I'll reply back when he has an update.
>
> Cheers,
> Josh, AdWords API Team
>
> On Tuesday, July 17, 2018 at 6:25:46 PM UTC-4, Zweitze wrote:
>>
>> This error was away at my site for quite a few weeks, but reappeared this 
>> morning. The response headers that came with the error were:
>>
>> Content-Disposition 
>> /bigstore/aw3-webapi-report-download/17144261fca9f85-0a63-4a20-9d9f-3f8d5baaf6e5/fileId-null-uuid-1fca9f85-0a63-4a20-9d9f-3f8d5baaf6e5-cid-1714426.tmp.xml.gz
>> X-Content-Type-Options nosniff
>> X-Frame-Options SAMEORIGIN
>> X-XSS-Protection 1; mode=block
>> Alt-Svc quic=":443"; ma=2592000; v="44,43,39,35"
>> Content-Length 0
>> Cache-Control private, max-age=0
>> Content-Type application/x-gzip; charset=UTF-8
>> Date Tue, 17 Jul 2018 04:42:09 GMT
>> Expires Tue, 17 Jul 2018 04:42:09 GMT
>> Server GSE
>>
>> The error occured with some old code running v201710.
>> CustomerId and ReportDefinition are available if necessary, but I can 
>> assure you that that same ReportDefinition (a PLACEMENT_PERFORMANCE_REPORT 
>> this time) was successfully used thousands of times.
>>
>>
>>
>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
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 and Google Ads API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to adwords-api+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/adwords-api.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/adwords-api/2a14dffe-9480-43cd-b8de-0486b0fabf1a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
  • ... Ronald Findling
  • ... 'Josh Radcliff (AdWords API Team)' via AdWords API Forum
  • ... Dorian Kind
  • ... 'Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum
  • ... Ronald Findling
  • ... 'Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum
  • ... Ronald Findling
  • ... 'AdWords API Advisor' via AdWords API and Google Ads API Forum
  • ... Zweitze
  • ... 'Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum
  • ... arthur . balduini
  • ... 'Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum
  • ... 'Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum
  • ... 'Josh Radcliff (AdWords API Team)' via AdWords API and Google Ads API Forum
  • ... arthur . balduini

Reply via email to