Hi @klaussner -
Thank you for the detailed feedback around the Confluence REST API v2. This is exactly the kind of feedback we are looking for, feedback that helps ensure we are working towards the best possible experience for our consumers.
I see that to achieve what you have outlined above with the V2 API, you need to make 6x the amount of calls with V2 vs. V1. For each page, you will need to fetch that page’s parent & the parent’s parent, and then fetch the corresponding content properties for each of those pages in a separate call.
We are working on a few new endpoints that will help out here. They are:
-
Get all ancestors of page→ given a page ID, will return a list of that page’s ancestors -
Get content properties for pages→ will return all content properties that correspond to the page type, and will include an array typepage-idfilter so response can be narrowed down to a set of pages- (there will also be
Get content properties for <type>for other content types)
- (there will also be
Once the above endpoints are released, the count of required calls from the V2 API will drop from 6 to 2. While we cannot promise this will be faster than V1, hopefully this will address: Even with maximal parallelism, the overhead of multiple REST v2 requests is so big that fetching the pages takes three times as long as the REST v1 implementation.
Please let us know what you think!
There will be examples outside of this one where sometimes the count of calls required to fetch the same set of content will increase from the V1 to V2 API. We are moving forward with this tradeoff for the reasons outlined in our blogpost here. However, we are confident this is a step in the right direction, and are excited to be working with the community in order to make this transition as smooth and performant as possible.
Thank you again!