It looks like this was a best offer sale, if you look up the item via sold listings on the website. I know there are problems with best offer sales via the Trading API at the moment (it's been broken for a good two weeks now), so it looks like this is also affecting findCompletedItems. I don't think any of the devs read these forums anymore (as most people's questions go unanswered), so I reported the bug (the Trading API one that I'm still getting) on Twitter through @AskeBay. You'll probably be best doing the same as well. You have to pay $75 otherwise through your developer account. It's quite outrageous that we can't report bugs without paying.
Here's my best guess as to what's happening... As mentioned earlier, that sample item is a Best Offer item. The eBay website, and most API calls, actually return the incorrect/false/asking price of the item, not the actual selling price. But it appears that findCompletedItems (fCI) does actually return the true selling price, although there's not much way to verify if that's true. So, the lower price being returned, $650, is probably the actual sold price, and the proper one being returned by fCI - when it works. $850 appears to be the incorrect/asking price of the item. Of course, fCI should return $650 consistently, so it seems like there's a bug on some of the API servers, as it were. It's as if some of the servers aren't being properly updated with final Best Offer selling prices, and thus only the false asking price is being returned in the meantime. I'm still seeing this bug currently, and I hope it's a temporary one.
I certainly understand that Ebay chooses to show one or the other price, but it seems nuts that the source of the price keeps changing when the API calls it - whether it's the lower or the higher, it should be consistent on subsequent searches. Certainly makes it difficult to determine which one to use/consider in the process. Hopefully they sort it out soon.
@helios825 fCI has always returned the best offer price since I started using the API, which is why this is such a big bug for me as my system relies on having the correct final price. It makes sense as well, as why would people _not_ want to know the actual price it sold for? I can understand eBay not showing this on their actual site, but the API should always return the correct selling price. @ilovethesmellofbiddinginthemorning - the more people that report this the quicker it should hopefully get fixed, so please get in touch with AskeBay on Twitter if you haven't already =)
**Just an FYI I’ve sent through a support request...** Thanks for doing that! (I assume you mean a paid support ticket through eBay Dev support portal.) If you haven't done so already, you may also consider adding to the ticket either of the following things; I've found these can make it easier for them to address bug reports: 1) An easy/quick sample API call that can be done in the browser, with simple page reloads, to demonstrate and reproduce the issue. When the support rep can see it with their own eyes, I suspect they'll be better able to construct the internal bug report. 2) Mention this thread in the support request. Please keep us posted! Thanks. -h
Yes, have submitted a paid support ticket. And yes I've included examples of the search strings and even screenshots in case they can't see the same results for whatever reason. In fact, now that I've taken note of the best offer items, I've run several searches since and only the eBay public site price is now shown in the API results and not the best offer (actual) selling price. It's possible this isn't a bug but a move by eBay to no longer show the best offer price even though their APIs. Not sure.
**I haven't heard anything back - does it normally take this long?** Remember, it's the weekend, and they keep normal biz hours in the eBay Dev support dept. That said, sometimes they're also backlogged during the week too. Hopefully it's not like that these days, and Monday you'll hear back. That theory occurred to me too, btw -- that perhaps eBay has formally stopped adding correct/final best-offer pricing to the fCI API call. Hopefully that's not the case, and it's simply a bug. But for now, it appears as though fCI is currently not getting updated with proper final sales prices for best-offer items. Or at least it's sporadic.