Platform

Platform

Manage, collaborate, search and distribute your highly-structured data across branches, versions and workflow-driven lifecycle.

Content Management

Create, Approve and Publish quality content to production on-time. Easy editorial and workflow tools let your best work reach your customers.

Automation

Automate your content creation and approval flows while taking advantage of AI services to enhance and curate content.

Publishing

Source and deliver high impact, quality content to your customers on schedule with automated assistants and scalable worldwide deployment.

Intelligence

AI agents work alongside your teams to help understand your content, search for documents and generate insightful answers.

Observability

Gain automatic insights into how your team works. Learn what do to make them more effective and improve customer engagement.
Use Cases

Health Care / Compliance

Work with automated sidekicks to quickly create, annotate and publish important content to physicians and patient-facing clinical teams around the world.

Train AI Models

Train AI models to be experts on your company contents and products to deliver customer recommendations, guidance and decision support.

Retail

Deliver your company branding, messages and product information to customers in real-time with scheduled publishing, hot fixes, A/B testing and versioned rollback.

Travel

Bulk load hotel, resort and travel information from internal data sources. Curate and publish to deliver real-time search and booking for live application customers.
Documentation
Developers
Pricing
Blog

How do I proxy API calls?

The /proxy path makes it possible for your authenticated UI users to access API resources.

A URL into the API typically looks something like this:

https://api.cloudcms.com/repositories/f0fb4efd3de07c54420a/branches/9bcdbfea8f2d900f0387/nodes/&lt;nodeId&gt;/attachments/thumb.jpg

To invoke this URL, you need to be authenticated to the api.cloudcms.com endpoint.

Users who are authenticated to the UI may opt to use the /proxy path to proxy their requests through the UI server and to the API. The proxied call is then executed against the API as though it were being invoked directly.

Thus, a user can invoke their method calls (GET, PUT, POST, etc) against a URL that looks something like this:

https://mycustomer.cloudcms.net/proxy/repositories/f0fb4efd3de07c54420a/branches/9bcdbfea8f2d900f0387/nodes/&lt;nodeId&gt;/attachments/thumb.jpg