WikiTraccs switches to Confluence Cloud v2 REST API
Note
The information in this post is relevant for Confluence Cloud only. There are no changes for Confluence on-premises.Background
Confluence Cloud so far provided programming interfaces (APIs) that allowed applications like WikiTraccs to treat it as no different that Confluence Server or Confluence Data Center.
Those days are over.
Atlassian is removing critical parts of the v1 REST API (that provided access compatible with the on-prem Confluence versions). Instead, applications are now forced to use the v2 REST API, starting December 2, 2024.
Note
Atlassian extended the deadline to March 31, 2025, shortly after writing this post.Here is the announcement by Atlassian:
What does this mean for users of WikiTraccs?
Ideally there should be no noticable difference. But the v2 API, in my view, is a step back in terms of developer convenience. More work has to be done to retrieve the same data as before.
From now on it takes both more time and more transmitted data to get the same work done as before.
WikiTraccs Update Required by December 2, 2024
Starting with version v1.21.3 WikiTraccs uses the new v2 REST API instead of deprecated v1 endpoints when talking to Confluence Cloud.
Starting December 2, 2024, using this or a newer WikiTraccs version is mandatory for Confluence Cloud to SharePoint migrations (unless Atlassian extends the deadline).
Until December 2, 2024, switching back to v1 API is possible. You can use the Force use of v1 REST API setting to switch back to v1:
If there are unforseeable issues, this setting can be used to check if those are caused by the switch to v2. It shouldn’t be necessary.
If you find issues, use any of the support channels to get in touch.