I think this is a recent bug that popped up. My client uses the Discourse as a service hosted by the lovely Discourse folks. We use the /posts.json API endpoint to list the 5 most recent posts from the forum on the website (https://forum.bonsaimirai.com/posts.json). We make this request server-side using curl.
Recently, we noticed that we were only ever seeing 3 or 4 of the most recent posts on our site. It looks like when the request is made without an API key, we end up seeing this very short list of recent posts. But when we use the API key with an API username, we see a greater number of posts.
We want the /posts.json endpoint to behave as it used to. We should be able to get whatever number of previous posts it used to deliver. If we use the API key + username, we end up retrieving posts that we don’t want to show to all users (from categories with user tier / group restrictions).
Are there new parameters available for the posts.json request that we can use to specify the desired number of results? Is this a bug that’s unique to whatever version of Discourse is being used for the hosted service? I notice that meta.discourse.org doesn’t exhibit this problem.