Problems with pagination result for GetMyeBayBuying Trading API call

[as-318687]

Hi,

I've been having issues trying to get all the items I've made an offer on and lost using the GetMyeBayBuying call from the Trading API. It seems that even if I specify a different page number the call still return only the first page. I do have enough items lost to fill 2 pages. Does anybody have similar issues? It worked fine 2 weeks ago.

[cardkingdom.com]

I just started having issues with sold items missing from this call.  But I AM seeing distinct pages.  Issue seems to have started mid-February.

[morielhezi]

Me too. I am using the WatchList on the GetMyeBayBuying call and seems to get an items array of 10 items only, regardless of the pagination. i.e., the response shows that the first page is returned with 35 items, for example, but regardless the items array returned contains only 10 entries. Issue started in the last couple of weeks indeed.

 

[morielhezi]

On the resulting xml the total number of items in the watchlist shows the correct number, but in the Items array I only get 10 items- and this is despite of the pagination parameters.

The WatchList used to return all my WatchList items (<100) in the response. Something bad has happened to the API of this method/service... 

[lihu-1049]

There's the same problem with the finding API, where even though it says there are 100 pages of results, going to any page outside of 1 returns no search results.

https://svcs.ebay.com/services/search/FindingService/v1?Operation-Name=findItemsAdvanced&Service-Ver...

[shipscript]

@lihu-1049 

I am currently using the Finding API and am not experiencing this pagination issue, so your call may be missing some details. 

https://svcs.ebay.com/services/search/FindingService/v1
?Operation-Name=findItemsAdvanced
&Service-Version=1.0.0
&Security-AppName=YOUR-APP-ID
&Response-Data-Format=XML
&REST-Payload
&keywords=shoes
&paginationInput.pageNumber=20

In your test case, searching on "shoes" will return 25 million items (25,398,727), thus, you should not see a shortage starting on page 2.  It wasn't until I added an item Filter that your query worked for me.

Here is the call that I use, hiding duplicate items, and substituting a keyword search to return a more reasonable number of items for more accurate testing:

https://svcs.ebay.com/services/search/FindingService/v1 
?OPERATION-NAME=findItemsAdvanced 
&SERVICE-VERSION=1.13.0 
&SECURITY-APPNAME=<$appid> 
&RESPONSE-DATA-FORMAT=JSON 
&GLOBAL-ID=EBAY-US 
&paginationInput.entriesPerPage=100 	// 100 max. 
&paginationInput.pageNumber=20   	// 100 max pages [1-100]. 
&keywords=nike%20air%20force%201%20men%20size%2014 	// nike air force 1 men size 14 (3800 items) 
&itemFilter(0).name=HideDuplicateItems 	// true will eliminate variations. 
&itemFilter(0).value=true

The findItemsAdvanced call will report the number of "items" (listings+variations), and there will usually be more listings+variations reported than actual listings. This is the same issue we see on the site search where the item total exceeds the number of available listings, and may not match the number of expected pages.  Regardless of the total number of items, eBay will display or return only 10,000 items - thus, with 100 items per page, there will never be more than 100 pages of results (not the 253,988 pages reported by the API response in your query.   If 7,000 of those 10,000 items are variations within the same listing, then only 3,000 listings will be returned in a request for 10,000. The pagination for 3000 listings will not match the expected pagination for 10,000 items.

Even in the case where I choose to hide duplicates, I must still test the results to see if the last page was reached, because, since Feb 2018, the pagination of actual "listings" on the site has not matched the pagination of the total "items" that the API reports.

[qwertylesh]

I came here to see if anyone else was reporting an issue i'm having where any feedback page on ebay pagination is broken, it will only show page 1 regardless of which pagination hyperlink is chosen. This problem with the GetMyeBayBuying call in this thread appears to be the same issue. I am using the .com.au ebay site fwiw. ebay will have to fix the UX or whatever underlying call is at issue.