Platform

Content Management

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

Enterprise Data Engine

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

Automate

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

Publish On Time

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

Train AI Models

Continuously train your own AI models as experts on your business, brand, products to engage with customers in real-time.

Reports and Analytics

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

Cloud CMS

Home

Getting Started

Data Engine

User Interface

Developers

Forms

Self Managed

Starts a job to find all the changes made in one branch that would be applied during a merge. The source branch is specified using the 'id' parameter. The target branch is the branch identified by the resource path. A view can be applied using the 'view' parameter (valid value is 'editorial').

POST /repositories/{repositoryId}/branches/{branchId}/changes/start

Parameters

Name	Required	Type
`repositoryId`	true	`string`
`branchId`	true	`string`
`id`	true	`string`
`view`	false	`string`
`filter`	false	`string`
`source`	false	`string`
`target`	false	`string`
`force`	false	`string`

Starts a job to find all the changes made in one branch that would be applied during a merge. The source branch is specified using the 'id' parameter. The target branch is the branch identified by the resource path. A view can be applied using the 'view' parameter (valid value is 'editorial').

Parameters

Response