Presently, as stated under https://developer.atlassian.com/server/confluence/pagination-in-the-rest-api - user can explicitly set the "limit" parameter to ensure how many results per page can be returned but then, there are hard limits for each entities such as 500 for content and spaces.

There are scenario's where pushing the max values for "limit" parameter for certain entities are really helpful(it makes that easy) from customisation perspective and they also does not pose any performance bottleneck. Citing above, it will be great if we can have a configurable parameter to override these present hard limits which can be tested on lower environment and can be used as a part of quick customisations.