tobie
Currently, the `count` query param is capped at `1000`. This is opaque to the user of the API which gets the same data set whether the `count` query param is set to `1000` or `100000000`. Instead of silently capping the value, I suggest returning a 4XX response with an appropriate error message when the `count` query param is bigger than `1000`.