cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Problems migrating from Shopping/Finding APIs to Browse API...

Hi there. I'm trying to migrate an automation for a client which uses the Shopping and Finding APIs. It's my understanding that these APIs will both be decommissioned in Feb of next year (correct me if I'm wrong).

 

This automation currently looks up listings (by IDs) and also searches for listings by seller ID and Title. To do this, I currently use GetMultipleItems and findItemsAdvanced.

 

It's my understanding that the replacement for these will be item/getItem and item_summary/search, but I'm having problems implementing these.

 

First, I was previously able to lookup multiple listing IDs at a time (20) with GetMultipleItems, but getItem can only do one at a time. There is another method (getItems), but it says it's only available to "select Partners". What does that mean, and how does one get access to getItems?

 

Second, I can no longer lookup all types of listings using the same call (GetMultipleItems). For single-sku listings, I have to use getItem, but for multi-sku variation listings, I have to use getItemByItemGroup. Isn't there any way to do a "smart" lookup which will return results no matter what type of listing it is? Basically, I  either have to know ahead of time what type of listing I'm using and use the appropriate methods, or I have to try one method, and if that method fails, try the second method.

 

Both of these issues will vastly increase the number of API calls I make per day which will almost certainly put me above the limit. I'm trying to figure out ways to reduce/simplify my API calls using these new methods.

 

Does anyone have any insight into how this can be accomplished?

Message 1 of 1
latest reply
0 REPLIES 0