The Cloud CMS API consists of an HTTP/HTTPS endpoint that uses OAuth 2.0 authentication. It supports both REST
concepts and asynchronous data operations. You can access this API using any of our drivers as well as
curl or any HTTP client library.
Our API provides functionality that covers all aspects of content production, publishing and presentation. 100% of the functionality of Cloud CMS is accessible from the API, including:
- Content Models, Creation and Editing
- Workflow, Scheduled Publishing and Release Management
- Users and Groups Management
- Role-based Authorities and ACL Security
- Binary Files and Attachments
- Versioning, Branching with Fork and Merge
- Query, Search, Traversal and Find Operations
- Replication and Content Transfer
- Data Warehouses and Analytics Capture
And much more.
The goal of this guide is to provide deeper information into the API, its object types and data stores that go beyond what is available in the developer Getting Started section and the API Explorer.
Getting Started for Developers
In terms of getting started with Cloud CMS and the Cloud CMS API, we recommend visiting our Cloud CMS Developers Page. These pages will guide you through connecting to Cloud CMS for the first time, getting your API Keys and setting up an account if you haven't already.
Cloud CMS API Explorer
The Cloud CMS API Explorer is a Swagger-based user interface that enables you to explore the Cloud CMS API from within your web browser. Using the explorer, you can authenticate and then fire off methods one at a time using the web interface.
The API Explorer is a good way to play around and try things. We also recommend using
curl to fire methods by
hand. The Cloud CMS SDK provides several
curl examples that you can use
as a starting point.
The Cloud CMS API Explorer also provides a Swagger compliant JSON file that you can use to potentially generate your own client stub code. Check out the Swagger project for more information.
Cloud CMS Drivers
Cloud CMS also provides drivers for a variety of languages that you can use to interact with the API programmatically. This can save you a lot of time, certainly, and can also inform your own custom development in terms of having working code that you can build upon.