New async "Convert content body" API does not support "wiki" conversion to "storage" but old API does

There is a change 2038 in Cloud changelog , posted 3 October 2024, regarding deprecation of the synchronous Convert content body v1 REST API.

The POST /wiki/rest/api/contentbody/convert/{to} endpoint will be removed on April 4, 2025.

It will be replaced by the new Async convert content body API.

The old API worked for “wiki” → “storage” format conversions.
The new API does not support this conversion (HTTP 400 Conversion between the given formats is not supported).

Our application relies on the ability to convert wiki to storage format.

Can the new API be made consistent with the API that it is replacing, with respect to supported conversions (btw, the API documentation for the old API does not accurately reflect the conversions it can do)? If not, can the old API be left in place to provide that functionality, or can you provide some other new API to do the wiki → storage conversion?

Thanks.

5 Likes

I opened a support case and Atlassian has opened a bug:

https://jira.atlassian.com/browse/CONFCLOUD-80503 " Loss of functionality with deprecation of the synchronous Convert content body v1 REST API in Confluence Cloud"