Deprecating many Confluence v1 APIs that have v2 equivalents

Hi all - it looks like I am limited to 3 replies so I will edit this last reply.

There are a number of things brought up in this post that have been addressed in the changelog here, please take a look!

Especially:

  • The Create page endpoint now allows a parent page to be specified
  • Attachment response entities now contain parent resource IDs
  • The content of the Link header is now also being returned in the body of the response
  • Convert content ids to content types

In regards to things that are in the works:

  • Ability to fetch space permissions (almost complete)
  • Ability to fetch page ancestors
  • Ability to fetch space icon (almost complete)

In regards to JavaScript parsing issue - this was an oversight on our part and a fix is coming soon! The ticket here can be tracked as well: [CONFCLOUD-75484] Confluence Rest API v2 IDs are in int64 which cannot be safely represented in JavaScript - Create and track feature requests for Atlassian products.

@TonyGoughAdaptavist - sorry for the oversight! There was a fix for these recently merged, it will like be in production by the end of the week.

There is also a new post that announces a change to the deprecation timeline here.

6 Likes