Authored by Victor Owuor, Senior Director, Software Development, Oracle
You are probably aware of our efforts to rebrand Content and Experience Cloud platform to offer a cohesive application suite that allows convenient development of applications, which take advantage of our product offerings. It is our intent to present a consolidated package of our feature set, abstracting away the different applications that comprise the Content and Experience Cloud product suite. A consolidation of our REST API is a critical part of that effort.
In previous releases, the REST API was in two separate packages, one for “Social” and another for “Documents.” That separation did not reflect the needs of our developers, who, for example, may need to obtain a conversation related to a document. Another use case that spanned both of those packages is a developer that wants to embed a document in a conversation. Those use cases are typical for developers and it is our goal to streamline the experience when write such applications. Other developer documentation, such as documentation of the Sites SDK or the DOCS Application Integration Framework was also separate. We have started making changes to the product and documentation to address those issues.
The REST service end-points will be as follows:
We have plans to do additional work to make it easier to develop using the API. The most important of those plans is our effort to harmonize the treatment of various common REST resources, such as people, groups, documents across the suite, which we hope to achieve later this year. We are also working to harmonize the authentication and security model across all REST end-points in the same timeframe.
Please try the new REST API and documentation and share any feedback or reaction in the comments.