[Urgent] Bug: Finding API Calls Often Returning HTTP-404 Error
Several of my Finding API calls have been returning HTTP 404 errors all day long. Not 100% of my calls, but many, perhaps in the 30%-70% range. I use a handful of the Finding API calls in my software/scripts, and it seems all of them are exhibiting this problem, such as findItemsAdvanced and findCompletedItems. For me, it started briefly around 1:00am (US Pacific Time) for a few minutes, then restarted around 10:28am and continues now. In my 7 years of using the Finding API, I don't think I'ver **ever** received a 404-error from the API. Many times re-calling the call, perhaps a few times is needed, will workaround the 404 and retrieve results, but it's a spotty process. Some of us in ePN-land are experiencing this and discussing it here (eBay Group join req'd):
http://community.ebay.com/t5/eBay-Partner-Network/API-404-errors/gpm-p/26981502 Anyone else experiencing this? eBay, can you please repair this promptly? (Thank you.)
Thanks everyone for your responses. I hope eBay sees this thread and takes immediate action. Good to hear the issue is reproducible in the API Explorer, so eBay Dev engineers can have something to work with. So, is there any reason why an API call might legitimately return a HTTP-404 error? I'm pretty sure 404 was meant for end-user non-API responses. I can't fathom why an API might want to return that, but maybe there's a good reason. BTW: FindItemsAdvanced (capital 'F') was part of the Shopping API before findItemsAdvanced (small 'f') from the Finding API was launched. The former was deprecated over 6 years ago. I'm surprised to hear it still works. That's awesome, if true.