Thank you for raising this issue. While we can see how this feature would be useful, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now.

Thanks again for your idea.

Bill Arconati,
Confluence Group Product Manager

And neither of them return total count of matching pages.

I also noticed that there are still discrepancies between the Remote API and the REST API:

• while the remote API doesn't support pagination of search results, the REST API does: http://docs.atlassian.com/atlassian-confluence/REST/latest/#id3540338
• but the REST API doesn't return an excerpt of the result, something that the Remote API does: http://confluence.atlassian.com/display/CONFDEV/Remote+API+Specification#RemoteAPISpecification-SearchResult

Christopher,
This sounds great. I am looking forward to it. Any rough estimate on the release timeline?

Hi Joe,

Thanks for the suggestion. We are currently revamping our search API for the next release of Confluence so we may look at supporting this when its complete. There is no reason that I can think of that we couldn't support this feature.

• This refers to the search method of the Confluence API, not the "remote search application"
• This is a request to support, more generally, the same type of pagination scheme one can find in the native Confluence application. That is to say, it would be great if the return results of the search method returned the total number of results found for that query, but it would also be great to have a page or result offset as a possible search parameter. The current implementation scheme is not usable as a search API. What good is it to get the first 10 results (using the maxResults parameter – which I would recommend be renamed to pageSize), if you cannot fetch the NEXT 10 results?
• Mei Yan's response in a personal email of "feature does come in handy, but do note that it may be too taxing on the application as it will have to process the searches, thus, causing it to run out of memory" makes very little sense. How is searching done in the native application without running out of memory? Doesn't the API call the same methods as the application?