3 ms·
I would go with POST with a body in that case, where I interpret is as a "new search item" and use GET to scan through results, if there are many results availa
by flowerbreeze 5y ago
I would go with POST with a body in that case, where I interpret is as a "new search item" and use GET to scan through results, if there are many results available. I don't think I've needed something like this more than once or twice though. From users perspective, asking information on specific 50 items at once is not something commonly done.
- 11235813213455 5y agoit's used for an export feature, where we join data from the client-side, not ideal, but for now it's a good compromise in terms of complexity for the API and client