I am confused as to whether the entire Confluence REST API v1 is going to get deprecated, or was it only a couple of things that have been deprecated already? looking at the atlassian changelog, i see this:
We are deprecating a number of v1 Confluence APIs (for a list, see “More details” below). On 1 February 2024, public access to these endpoints will be removed. If you’re currently using these endpoints, you’ll need to migrate to the v2 APIs found here: The Confluence Cloud REST API.
Updated 30 Nov 2023: We are extending the deprecation period for all endpoints noted in this changelog to at least June 2024 and will announce a new date soon.
Updated 3 May 2024: We are extending the deprecation period for all endpoints noted in this changelog to 2 Dec, 2024.
Updated 27 Nov 2024: We are extending the deprecation period for all endpoints noted in this changelog to 31 March, 2025.
Updated 19 Mar 2025: We are extending the deprecation period for all endpoints noted in this changelog to 30 April, 2025.
The full list of APIs being deprecated is as follows:
All Content Property endpoints: The Confluence Cloud REST API
Update inline task given global ID: The Confluence Cloud REST API
The links no above no longer work, the endpoints probably do though until their deprecation date (which keeps on getting pushed). So does this mean that all other endpoints that are visible and not listed in the full list will not be deprecated and can be safely used?
Hello @omer_abdullah
No. The 1 Aug 2023 changelog entry was for the specific v1 endpoints listed in that notice, not for every v1 endpoint. In your text, that list is basically the Content Property endpoints plus Update inline task given global ID.
The wording Atlassian used later is also important. In the follow-up timeline post, they said they planned to remove all v1 APIs currently marked as deprecated. That is narrower than “all v1 APIs.” They also later carved out some children/descendants APIs with a different extension date, which again shows this has been handled endpoint by endpoint, not as one blanket removal of all v1.
Also, as of now, Atlassian still has live v1 documentation for other Confluence Cloud API groups like content, users, search, and space. So v1 as a whole is clearly not gone. At the same time, Atlassian is still publishing new endpoint-specific v1 deprecations, for example the Convert content body v1 REST API deprecation that is currently extended to Aug 5, 2026.
@Arkadiusz Wroblewski thanks for the prompt reply. A slightly different follow up, but does the v1 api support comment addition to confluence pages, or is this one of the endpoints that was deprecated. I cannot find any relevant changelog or endpoint regarding this
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.