Confluence XML-RPC APIs

[Ayaskant Swain]

Hi,

Currently i am working on migrating our organization's pages from Mediawiki to Confluence. After doing some search on internet i came to know about UWC (Universal Wiki Converter) https://migrations.atlassian.net/wiki/spaces/UWC/overview tool, which is a tool developed by Atlassian some years ago to help users in migrating pages from different Wikis to Confluence. But currently no active development is happening for this tool and it is not supported by Atlassian now. But since it is a open source tool, Atlassian suggests to use the code of this tool as a base and modify it according to one's need to migrate the pages to Confluence. That will save a lot of coding effort if we write code for a new tool from scratch.

While thats what i am doing, i found that this tool is internally calling Confluence's old XML-RPC APIs and not the new RESTful APIs to push the page content. My question is will Atlassian keep supporting the XML-RPC based API in future? Do i need to modify the code of UWC tool to call the REST APIs which are the new ones ? The later option will need more effort, i guess. Our Confluence version is 5.x.

Thanks

Ayaskant

[Stephen Deutsch]

One option you might consider is using Pandoc to try to convert your mediawiki pages, and then you can use this converter plugin:

https://bitbucket.org/atlassianlabs/confluence-pandoc-connect/src/c3c8f8c32e88e4b2f36ac0160f411c5ffb3b64ee/resources/confluence-storage.lua?at=master&fileviewer=file-view-default

https://github.com/jpbarrette/pandoc-confluence-writer

https://gist.github.com/zhzhxtrrk/11106681

to convert to Confluence Storage Format. You can try using the Universal Converter for Confluence Cloud (which is where the pandoc converter plugin comes from)

https://marketplace.atlassian.com/plugins/com.atlassian.confluence.pandocconnect/cloud/overview

to try to convert your pages (even if you don't use Confluence Cloud, you could always use it for testing and then export to one of the most recent Server versions), but I've had mixed success with that tool as well.

[Minh Tran]

@Ayaskant Swain XML-RPC and SOAP APIs are deprecated since Confluence 5.5

You can check it out here https://developer.atlassian.com/server/confluence/confluence-xml-rpc-and-soap-apis/

That means these API can be removed anytime. I suggest you to switch to REST api where it is possible

[Ayaskant Swain]

Hi @Minh Tran - Thanks for replying. Yes even i am thinking to switch to the REST APIs as the XML-RPC APIs might be removed anytime.

Need some info on migrating form the XML-RPC based APIs to REST APIs. Since teh request payload will be different to call a REST API how big is the effort to change the code of an existing XML-RPC client so that it can make a call to REST APIs. e.g. -calling the Create Content API. - POST /rest/content

https://docs.atlassian.com/atlassian-confluence/REST/6.6.0/#content-createContent

Thanks

Ayaskant

[Minh Tran]

Here is the latest documentation @Ayaskant Swain https://docs.atlassian.com/ConfluenceServer/rest/latest