Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Pagination not working when using search API with text searches

We are using search API of confluence cloud(


We are performing text searches with the above API.


Example of our query is below:

https://mydomain/wiki/rest/api/search?limit=2&start=1&cql=type=page and space='TS' and title='test'

We have already have 7 records matching when we use only limit=10, one first call limit=2&start=0, I am getting 2 records but when I use limit=2&start=1 or limit=2&start=2 or 'start' more than 0, I am getting empty array in results of the API. Ideally we should get the paginated records in the results of the API, but from API we are not getting proper response.


Does Anybody faced the similar issue or had a solution for the above problem?




3 answers

Same case here ...   is there a bug open for this? 

EDIT: sorry, I'm using Confluence SERVER search API.  I'll leave this post here in case other server devs end up here.  Pagination of the search API is hard to use and broken in some cases:



I'm using the search REST API and the "next" link in the results from my first call doesn't work.  It returns HTTP 400 Bad Request, saying that the "CQL query parameter is required but was empty".

I think it is odd that the search API (first request, no pagination params specified) works if an "=" that is contained in the value of the cql param is not URL encoded (like /rest/api/content/search?cql=macro=multiexcerpt). 

It also works if the "=" IS URL encoded (like /rest/api/content/search?cql=macro%3Dmultiexcerpt) which I would expect.  Why would the API allow unencoded cql parameter values?  That is so odd and feels like it is never going to work.



This works for me (SERVER API).  I worked around any oddness in the API for parsing the cql parameter value by always encoding it and specifying it separate from the parameters for pagination:

1st request:

curl --user username:password -G "" --data-urlencode "cql=macro=multiexcerpt"

2nd request:

curl --user username:password -G "" --data-urlencode "cql=macro=multiexcerpt"


We're running into a similar issue where,content.history.lastUpdated

returns the same value regardless of what start is set to. We have 72 results listed, but we can't access them for some reason by changing start.

I'm seeing this same issue with Confluence Cloud version 1000.0.0-f582da98b37a.

I increase the start value and the CQL JSON reply shows the correct start value but the content is always the same. I can only access the first 200 results no matter what start is set to.

Is there a solution or workaround for this?

Suggest an answer

Log in or Sign up to answer
Site Admin

Atlassian Community Events