Web API antipattern- so the use case is to things in a collection. But it isn't a full query language, so you have to scan & check each row. But the API only offers a way to fetch things 1x at a time. And it is rate limited. So really, to do anything I have to
replicate the entire dataset (fetch everything, cache all of it, run a filter locally on the full cache). So really, all the endpoints should be set up for this usecase, all endpoints for other use cases are nerfed by the rate limiting.
♡ 0 ↻ 0In otherwords, when you design a public API, think about a bunch of ways it might be used and see if it is so painful to use the current interface that everyone will switch to downloading every !#$#@$ row, which is exactly what rate limiting is trying to discourage.
♡ 0 ↻ 0