[ENDPOINT] Proposed design change for getListings - multiple states

[kievins]

Current Endpoint Design Currently it's possible to only query one listing state (active, draft etc) per request.

Proposed Endpoint Design Change Should allow to pass multiple returnable listing states for a request.

Why are you proposing this change? In our use case we require almost all listing states to be pulled in on regular intervals (multiple times a day). Having to request listings separately for each state significantly increases the overall request count for stores with smaller amount of listings.

[benjymouse]

+1

[NellyGzzA]

Hi @kievins ! Thank you so much for this proposal and for sharing your use case. Being aware of these situations and suggestions like yours will help us figure out how to design the endpoints and prioritize them.

[cal-tec]

It is over a year since this was suggested, I have a real usecase for this also... Please can we all have an update on where you are at with it internally

[etsyachristensen]

@cal-tec Which endpoints would you be wanting to make this query on? It's helpful to have a use case in mind as we evaluate the options. Changing the endpoints to accommodate this may be a larger lift than we can do at the moment, but having just the few requests on it so far hasn't made it a huge priority. If the data weren't available any other way, it would certainly be much higher on our list. However, can effectively retrieve the requested data via separate calls.