The maximum allowed number of resources per page in a search result (for example /ers/config/endpoint) is limited to only 100 resources. Is there a legitimate reason for this low number?
The amount of data sent in responses is usually very small, I would think that the work with handling paging request for an ISE database with a few hundred thousands endpoints require more CPU and RAM than sending all of them in one response - or at least have the ability to send 10000 at once.
The API has some bulk handling, but not for search requests. I can't find any efficient way to retrieve the endpoints and their id's other than paging through /ers/config/endpoint responses, which takes much more time than it should.
