Streamline Development with Automatic Publishing and Unpublishing
Now, developers can publish content items immediately after importing them and integrate with external services automating the publishing process. Read on to learn more.
Yvette HastingsPublished on Feb 12, 2019
The Kentico Cloud Content Management API (CM API) was originally designed to provide read/write access to your content. In a nutshell, the secure REST API helps developers migrate existing content into a Kentico Cloud project, and update content in unpublished content items.
But as market needs continue to evolve, we recognize that developers could benefit from even more CM API capabilities. As a Content as a Service CMS is usually part of a complex environment consisting of multiple services, the need to synchronize between them grows. That's why we have extended the CM API so that you can use it to publish, unpublish, and create new versions of content programmatically. What's more, you can now even use it to move the content between workflow steps.
Leverage More Content Management API Capabilities
So what does it mean for you and how can you leverage this new functionality in your projects? With automatic publishing and unpublishing, you will be able to:
- Publish content items immediately after they are imported
- Automate the publishing process (releases)
- Replace many images at the same time
- Process content by a third-party service
- Fill out additional fields – e.g., product info
- Handle translations for multiple languages
Read our CM API article in the Kentico Cloud Developer Hub to learn more.
It Doesn't Stop There
We are always looking ahead. A few key areas we are exploring include:
We are looking to extend webhooks so that you can automatically process content before it's published, which would allow you to send notifications when a workflow step changes and react to it. For example, you could send a Slack notification when a content item is ready for review, or send the content for translation by setting it to a "ready for translation" workflow step.
CM API Token Expiry Update
Currently, the CM API token expires after 90 days, which is great for initial imports, but we have listened to your feedback and we're going to implement a non-expirable token for outgoing integrations.
Create a Sandbox
We are also working on support for Continuous Integration, so you will be able to create a sandbox for testing your content model changes or synchronize between environments using our Content Management API.
Talk to Us
We'd love to know more about your integration scenarios and if you have a use case for these new CM API capabilities. Get in touch now, as we would be happy to discuss the future development of our CM API based on your requirements.