[FIXED] UNEXPECTED_INTERNAL_API_ERROR for all requests

207 views
Skip to first unread message

AdWordsApiUser

unread,
May 3, 2019, 1:38:50 PM5/3/19
to adwor...@googlegroups.com
Hi Team,

The API is down with UNEXPECTED_INTERNAL_API_ERROR for any request. 

Thanks for your help!

di...@adscale.com

unread,
May 3, 2019, 1:43:04 PM5/3/19
to AdWords API and Google Ads API Forum
Same here.

googleadsapi...@google.com

unread,
May 3, 2019, 3:02:34 PM5/3/19
to AdWords API and Google Ads API Forum
Hello, 

Our team is looking into this. Could you please confirm if you're still seeing this issue? If so, could you please retry the request and share the request/response logs which includes the request Id to check this further? You can share the details via Reply privately to author option.

Regards,
Bharani, Google Ads API Team

Was your question answered? Please rate your experience with us by taking a short survey.
If not -- reply to this email and tell us what else we can do to help.

Take Survey

Also find us on our blog and discussion group:
http://googleadsdeveloper.blogspot.com/search/label/adwords_api
https://developers.google.com/adwords/api/community/

googleadsapi...@google.com

unread,
May 3, 2019, 3:46:16 PM5/3/19
to adwor...@googlegroups.com
Hello, 

Thank you for reporting this. There was an outage on May 3rd from 10:22 - 10:48 Pacific time for the Google Ads API and AdWords API. This issue has been resolved now. Could you please retry the API requests that failed during that time and let us know if you have any issues?


Regards,
Bharani, Google Ads API Team

Ross Seeman

unread,
May 8, 2019, 5:07:03 PM5/8/19
to AdWords API and Google Ads API Forum
Hello, 

 My advertisers are asking if the reporting data in AdWords has been fixed from May 2-3? This site seems a little outdated, and I want to make sure I give them the thumbs-up before they bill their clients. 

-Ross 

googleadsapi...@google.com

unread,
May 9, 2019, 9:12:15 AM5/9/19
to rosss...@google.com, AdWords API and Google Ads API Forum
Hi Ross, 

We are actively working on correcting the data from 12:01am on May 1 to 4:00am May 2 (PDT). You can find the latest updates regarding this in the blog post here

Let me know if you have any other questions.
Reply all
Reply to author
Forward
0 new messages