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

REST API: How to retrieve a list of recently archived pages?

Is there any way to retrieve a list of recently archived pages?

  • I know it is possible to retrieve archived pages via:


but it is not possible to use sorting here.

  • On the other hand, I can use search and sorting


but this does not list the archived pages for me.

I saw that there is a parameter (includeArchivedSpaces), but I don't think I understand how it works (does the whole space have to be archived?). For example:
an archived subpage is not returned by the API despite the parameter being set rest/api/content/search?cql=lastModified=2023-04-20%20and%20type=page&includeArchivedSpaces=true

any other suggestions?

1 answer

0 votes
David Bakkers
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Apr 21, 2023 • edited

Hello @Agnieszka Korotkiewicz 

With regard the includeArchivedSpaces parameter; Yes, that is for finding content within a space that has been archived. That parameter is not for finding content that has been archived.

It seems that you didn't notice the cqlcontext parameter that can be used with the Search content by CQL endpoint:



string.The space, content, and content status to execute the search against. Specify this as an object with the following properties:
  • spaceKey Key of the space to search against. Optional.
  • contentId ID of the content to search against. Optional. Must be in the space specified by spaceKey.
  • contentStatuses Content statuses to search against. Optional.


So, your query would be:


The reason for the funky encoding of the cqlcontext parameter is that it expects a JSON object with all the values, so you have to URLEncode it all :(

Refer to this article where it's been discussed before.

Thank you for your reply. I saw this option, but I tried to add this parameter as a string and it didn't work. However, reading carefully the part of the documentation you sent, I noticed that it should be an object...

Thank you for your help!

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events