Confluence REST API v2: Update to v1 Deprecation Timeline

Hi @AshishShirode @HughWu or others:

I am glad to see the recent addition of “include-xxxxx” query parameters in CHANGE-1420. Are there plans to bring this change to custom content? (As well as possibly databases and whiteboards?)

If an application needs to be able to deal with all of the various primary content types, it is quite complicated if there are “shortcuts” to fetch this information with certain content types but not the others. For example, if “include properties” or “include operations” are available only for pages and blogposts, then developers still need to write and test the code to fetch these items separately anyway. This is no less work than before, operations become oddly slower for only one specific content type, and it introduces another code path that needs to be tested separately.

5 Likes