{"action":"created","issue":{"url":"https://api.github.com/repos/WP-API/WP-API/issues/2316","repository_url":"https://api.github.com/repos/WP-API/WP-API","labels_url":"https://api.github.com/repos/WP-API/WP-API/issues/2316/labels{/name}","comments_url":"https://api.github.com/repos/WP-API/WP-API/issues/2316/comments","events_url":"https://api.github.com/repos/WP-API/WP-API/issues/2316/events","html_url":"https://github.com/WP-API/WP-API/issues/2316","id":136206422,"number":2316,"title":"Way to remove limit on result set","user":{"login":"stonetip","id":3766798,"avatar_url":"https://avatars.githubusercontent.com/u/3766798?v=3","gravatar_id":"","url":"https://api.github.com/users/stonetip","html_url":"https://github.com/stonetip","followers_url":"https://api.github.com/users/stonetip/followers","following_url":"https://api.github.com/users/stonetip/following{/other_user}","gists_url":"https://api.github.com/users/stonetip/gists{/gist_id}","starred_url":"https://api.github.com/users/stonetip/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/stonetip/subscriptions","organizations_url":"https://api.github.com/users/stonetip/orgs","repos_url":"https://api.github.com/users/stonetip/repos","events_url":"https://api.github.com/users/stonetip/events{/privacy}","received_events_url":"https://api.github.com/users/stonetip/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2016-02-24T22:27:27Z","updated_at":"2016-02-25T12:57:59Z","closed_at":"2016-02-25T12:57:59Z","body":"In more recent versions of the API, results are limited to 100  per request. I can appreciate why this would be a good thing with a public-facing, unrestricted API. However, it means our calling code has to have paging loops written into it for every action, such as getting all the posts for a category to use in a server cache. And it means making multiple HTTP requests.\r\n\r\nIt'd be great if there was some way (other than hacking an installed copy) to remove this limit. My thought is authenticated users could be allowed to do this."},"comment":{"url":"https://api.github.com/repos/WP-API/WP-API/issues/comments/188776865","html_url":"https://github.com/WP-API/WP-API/issues/2316#issuecomment-188776865","issue_url":"https://api.github.com/repos/WP-API/WP-API/issues/2316","id":188776865,"user":{"login":"danielbachhuber","id":36432,"avatar_url":"https://avatars.githubusercontent.com/u/36432?v=3","gravatar_id":"","url":"https://api.github.com/users/danielbachhuber","html_url":"https://github.com/danielbachhuber","followers_url":"https://api.github.com/users/danielbachhuber/followers","following_url":"https://api.github.com/users/danielbachhuber/following{/other_user}","gists_url":"https://api.github.com/users/danielbachhuber/gists{/gist_id}","starred_url":"https://api.github.com/users/danielbachhuber/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/danielbachhuber/subscriptions","organizations_url":"https://api.github.com/users/danielbachhuber/orgs","repos_url":"https://api.github.com/users/danielbachhuber/repos","events_url":"https://api.github.com/users/danielbachhuber/events{/privacy}","received_events_url":"https://api.github.com/users/danielbachhuber/received_events","type":"User","site_admin":false},"created_at":"2016-02-25T12:57:59Z","updated_at":"2016-02-25T12:57:59Z","body":"> There really needs to some config options for the API settable from a dashboard or, at worst, in a config file.\r\n\r\nWordPress has actions and filters for this purpose. You can filter the endpoint registration args to remove the `maximum` attribute:\r\n\r\n```\r\nadd_filter( 'rest_endpoints', function( $endpoints ){\r\n\tif ( ! isset( $endpoints['/wp/v2/posts'] ) ) {\r\n\t\treturn $endpoints;\r\n\t}\r\n\tunset( $endpoints['/wp/v2/posts'][0]['args']['per_page']['maximum'] );\r\n\treturn $endpoints;\r\n});\r\n```"}}