question

Same here! I went through to support but seemingly the only way to contact Ebay is via Premium Support which I don't have.

There must be loads of us in this situation!

It's a shame that it's such short notice to deprecate and disable the API. I am certain that products such as pricecharting among many others will cease working. It costs $75 to even be considered for the Insights API.

My product will be out of action until I can come up with a good solution to this API disappearing. I drive all my traffic away from retailers and towards eBay by using data from findCompletedItems to show that eBay is cheaper than other third party retailers.

Bit disappointed.

EDIT: Is there any word from eBay on this or any workarounds? Cheers!

Same, I've had a product for sale since 2013 using this API and to give developers only a few days notice and no real accessible alternative is absolutely ridiculous. I have 10k daily active users who have all paid for my product for whom my product will literally be rendered useless in 9 days time. I am not looking forward to the fallout from that.

I hope someone from ebay is reading this and is able to give us more sensible timeframe to go through the approval process for the new API and to update our products accordingly, especially as we've been given 9 days and the application itself takes up to 10 working days and requires PCI certificates etc, since its an application for all Buy APIs, 90% of which are not required to replace the findCompletedItems functionality.

I use the FindCompletedItems call in my custom listing application to get a price recommendation when I'm listing new items. I suppose an alternative method could be implemented using JSoup to send a Get request and then parsing the result.

Example search:

https://www.ebay.com/sch/i.html?&_nkw=radio&_sacat=20081&LH_TitleDesc=0&LH_ItemCondition=3000&LH_Complete=1&LH_Sold=1

This is your keyword(s): &_nkw=radio

This is the search category: &_sacat=20081 (use 0 for all categories)

Whether you want to search title and description: &LH_TitleDesc=0 (use 1 to also search desc)

Item condition: &LH_ItemCondition=3000 (3000 = used)

Return completed items only: &LH_Complete=1

Exclude unsold completed items: &LH_Sold=1 (0 returns sold and unsold)

You can experiment by searching on eBay and seeing what changes in the URL when you check different boxes in the sidebar.

If you have a distributed app and implement such an alternative, I would be certain to make the requests originate from the client-side application and go direct to eBay, rather than have the client send request to server, and then the server get the data from eBay. Of course, if the client isn't written in Java, then JSoup wouldn't work, but I'm sure something similar would be available for different programming languages.

I'll have to experiment later, but perhaps we could also just use FindItemsAdvanced. The SellingState token can return the following selling state values just as FindCompletedItems could.

Active

The listing is still live. It is also possible that the auction has recently ended, but eBay has not completed the final processing (e.g., the high bidder is still being determined).

Canceled

The listing has been canceled by either the seller or eBay.

Ended

The listing has ended and eBay has completed the processing of the sale (if any).

EndedWithSales

The listing has been ended with sales.

EndedWithoutSales

The listing has been ended without sales.

Does deprecated mean the API won't be available on October 15? There is an API deprecation page which shows two states: deprecated and decommissioned. The decommissioning date is about 6 months after deprecation.

https://developer.ebay.com/docs/api-deprecation

Does deprecated mean the API won't be available on October 15?

Deprecated means planned to be discontinued, but still active. But eBay regularly misuses it to mean deactivated.

The email says it will be deprecated, restricted and no longer accessible.

For now, you could log item numbers of interest with Browse or Finding API and pull the sales data from Shopping API after the items end. Check terms to see if that's permitted.

That's really annoying that this is happening on such short notice. It's quite literally the only API I use from eBay.

However, one reason maybe that it potentially breaches GDPR. I am in the UK (which is no longer in EU but still has GDPR laws) and have noticed that the sold items include post codes (zip codes) even for private sellers where they should be redacted.

I guess it's about of a tinfoil hat conspiracy on my behalf but that's one reason I can see it happening. The only reason I noticed it is because someone asked me how much is a fair price of a product that they themselves previously owned whilst I was debugging (so I printed the items to console - not stored) and they noticed their post code there.

same here :-(

Has anyone had anymore progress on this? My app solely relies on getting prices of sold items using this API. Other than Marketplace API, is there another option at all?