What is changing? Hello everyone, Confluence Cloud is announcing the start of a deprecation period for a number of v1 API endpoints, please see the changelog: https://developer.atlassian.com/cloud/confluence/changelog/#CHANGE-864 for full details. We intend to remove public access to these endpoin…

Thanks @TonyGoughAdaptavist for sharing. I guess this apply to UI Kit right, and not CustomUI? As far as I have tested so far CustomUIs are still not supported for the export/print/history view.

@ErikUnemyr This is for Connect macros, I’m not sure how Forge ones are affected.

Hi Team, Any updates to this query posted a week back is appreciated. Thanks [image] Deprecating many Confluence v1 APIs that have v2 equivalents Confluence Cloud Announcements Hello, I have posted my query here Unable to find page's tinyui, base and webui But reposting…

Hi Team, Have you just removed xxxIdString fields from v2? If so, is v2 considered stable now? If not, how is the deprecation period for v1 set? We migrated our code to v2 using those fields. It is broken before we release it and we have to change it to use different fields. "parentIdString":"…

Hi @jens - this is not currently planned but if there is enough of an ask for this we will get it prioritized! Hi @TonyGoughAdaptavist - this is great to hear! Hi @sunita - I don’t have an answer yet but will work on making sure someone looks at this soon. I can confirm this is present in V1 and n…

@SimonKliewer , After experimenting with the v2 API, I encounter a problem: https://developer.atlassian.com/cloud/confluence/rest/v2/api-group-content/#api-content-convert-ids-to-types-post returns the content type as a singular, e.g. page. However the API to get page properties needs the plural …

The link you provided did not mention anything about the removal of idString fields. That is breaking change. Nobody knows whether it is “briefly” in production. It was IN production.

[image] eagle.xiao: It was IN production. Big +1! @SimonKliewer Please carefully review what happened here and make sure you grasp the consequences of releasing undocumented breaking changes to a public API so nonchalantly! We had already started using the idString fields. If that code would…

Exactly. Our PR was ready before easter. If it were not due to easter holiday, we would have released the change for migration which uses idString fields. @SimonKliewer , can you please confirm whether V2 API now finalised? I mean truely finalised or locked to a version. We cannot develop against a…

Hey there :wave: , just wanted to give some feedback in regards to: [image] SimonKliewer: Now, if you utilize the serialize-ids-as-strings param you should be good to use this to change the return type of the existing ID fields! For me, it feels a bit wierd that this is passed as a query-pa…

The Atlassian Developer Community

Deprecating many Confluence v1 APIs that have v2 equivalents

Confluence Development Confluence Cloud Announcements