Is there a difference between server-based and cloud-based Confluence REST API?

[ibuchanan]

Welcome to the Atlassian developer community @gergelyignacz,

@gergelyignacz

• Is the REST API for the server-based and for the cloud-based Confluence the same?

No. The biggest change is that Confluence Cloud uses a different underlying format for content called Atlassian Document Format. And there are pending APIs being deprecated from v1 in favor of new v2 APIs that don’t exist in Confluence on-prem. From a quick scan of the source code for that Python lib, I don’t those difference reflected.

@gergelyignacz

• If not, is there a comparison sheet of the differences available?

No. I’m not aware of any comprehensive resource for that.

@gergelyignacz

• Can I use the Confluence python API the same way for both cloud and standalone server?

Given the differences explained above, I don’t recommend trying. The abstractions are too far apart now over years of “drift” between DC & Cloud as different products.

Although written about a different Python library and about Jira Cloud, here’s my advice about using Python to talk to our Cloud REST APIs:

Mock Jira API for Jira Python Library

@AdrienMerat, My first reaction is don’t use the pycontrib lib for Jira. While I greatly appreciate that people invest their own time and energy into open source contribution, I hear about a lot of problems using that library. The last time I looked (just a few days ago, it looked like that library made a lot of strange assumptions that would confound sane unit testing, like needing to GET a Jira issue before allowing a PUT. As I recommended then (and cross-posting and elaborating here for furt…