Can someone comment on the the status of this ticket, vs seemingly similar work in #1522?

Is this, or the other MR, required for this library to actually support Confluence Cloud servers that are deployed with the v2 REST API? Without this work, is this library not usable in that context?

Hi — just wanted to signal interest in getting this across the line.

I've been working on a pagination fix for get_all_* methods (PR #1616) and in the process ran into the exact problem this PR solves: api.atlassian.com Cloud users hitting 401 "scope does not match" because the library defaults to wiki/api/v2, which requires OAuth2 app credentials that most users don't have set up. I opened an issue (#1618) for it but closed it in favour of this PR, since a proper v2 implementation is clearly the right fix rather than a workaround.

A few questions to understand where things stand:

• Is there anything blocking a review/merge? The PR has been open since April 2025 and there seems to be community demand for it (see also Confluence New Implementation is documented, but not available in a release #1588, [Confluence] Does not use the v2 version of the api-rest #1200, 401 with scoped access token #1546).
• Is there anything I can help with — rebasing on latest master, adding tests, splitting into smaller reviewable chunks?
• How does this relate to Confluence api v2 and Jira api v3 added #1522? Are they competing approaches or complementary?

Happy to contribute if it helps move this forward.

🤖 Generated with Claude Code

Hi, also confirm interest here. We'd like to reduce our permissions' scope from our access tokens and waiting for v2 to be available.