---
title: Get started with Content Management API
slug: cms-12/api
docTags: 
createdAt: 2026-08-07T16:45:43.000Z
---

:::hint{type="info"}
**Note**
The Optimizely Content Management API is available for only Optimizely Content Management System (CMS) version 12 and *not* version 11. Optimizely decided not to back-port this package.
:::

The Optimizely Content Management API adds REST endpoints for basic content management operations such as:

- Create content objects
- Modify existing content objects
- Delete content objects
- Get draft content objects
- Move content objects

The REST API is useful for pushing external content to Optimizely without deploying custom integration code to the Optimizely Content Management System (CMS).

See also [Content Management API reference](docId:0ABwZzeRL5_hdHuKyEdQ1) for the REST API service layer.

## Create

Creates a content object of the desired type under a parent. The endpoint also can be used to create a language branch for existing content.

- `POST /api/episerver/v3.0/contentmanagement`

## CreateOrUpdate

If the content already exists, then the endpoint updates the content object. If it does not exist, a content object is created. This endpoint cannot be used to update the content hierarchy.

- `PUT /api/episerver/v3.0/contentmanagement/{contentGuid} ## Delete`

Moves the content object to the trash bin or permanently deletes it.

- `DELETE /api/episerver/v3.0/contentmanagement/{contentGuid}`
- `DELETE /api/episerver/v3.0/contentmanagement/{contentReference}`

## Get

Returns the primary draft or latest published version of a content object.

- `GET /api/episerver/v3.0/contentmanagement/{contentGuid}`
- `GET /api/episerver/v3.0/contentmanagement/{contentReference}`

## Move

Moves the content object to become a child of the target ID.

- `POST /api/episerver/v3.0/contentmanagement/{contentGuid}/move`
- `POST /api/episerver/v3.0/contentmanagement/{contentReference}/move`

## Update

Update the primary draft or latest version of a content object. This endpoint is ideal for changing a part of content, especially content status (for example, making it published) if needed. This endpoint cannot be used to update the content hierarchy.

- `PATCH /api/episerver/v3.0/contentmanagement/{contentGuid}`
- `PATCH /api/episerver/v3.0/contentmanagement/{contentReference}`