the funciton lackness of REST API v2 compared with v1

[Zhichao Wei]

Hi Team, I have observed that the REST API structure for Data Center is formatted as 

http://host:port/rest/api/resource-name

as outlined in the document, and it contains complete functions.
In the Cloud environment, there are both v1 and v2 versions of the REST API. The v1 version utilizes 

http://host:port/wiki/rest/api/resource-name

but it offers limited functionality, such as the inability to create pages, as indicated in the document.
Conversely, the v2 version employs /wiki/api/v2/resource-name and similarly lacks certain functions, including the capability to create attachments.

Why are v1 and v2 responsible for different functions in Cloud?

Should I understand that Data Center API = Cloud API v1 ?

Thanks. 

[Thiago P _Atlassian Support_]

Hey there @Zhichao Wei ,

Although they provide similar functionalities, the REST API endpoints for Cloud and Data Center are independent from each other.

Our documentation for those is below:

• Confluence Cloud REST API v2
• Confluence Cloud REST API v1
• Confluence Data Center REST API

In Cloud, the v2 is an improvement on definitions and performance over the original v1, but since not all functions were already ported, both currently coexist.

In Server and Data Center, the REST API endpoints are an evolution of the former XML-RPC and SOAP APIs that are deprecated since Confluence 5.5.

As an example, the Create Page endpoint is available in v2 and since that's an improved version, it was deprecated from v1.

Hope this helps!  =]

[Aron Gombas _Midori_]

I would say, that on Cloud:

• If you can solve a problem with "v2", solve it with "v2".
• If you can't solve a problem with "v2" and have to use "v1", only in that case use "v1".

(You can freely mix the two.)

[Thiago P _Atlassian Support_]