CMS Contents

Create managed content.

Resource

1/connect/cms/contents

Available version

54.0

Requires Chatter

HTTP methods

POST

In version 56.0 and later, you can upload binary files to create managed content. To upload a binary file, you must send it in a multipart/form-data request. For information about how to create the multipart/form-data message, see Uploading Binary Files.

Request body for POST

Root XML tag

<ManagedContentInputRepresentation>

JSON example

1{
2"contentSpaceOrFolderId":"0Zuxx00000003M5CAI",
3"title":"Title of Document",
4"contentType":"ftestSfdcOnly__banner",
5"urlName":"testUrl",
6"contentBody" : {
7   "bannerImage":"MCZOCY2AM5PFBADN5UDRB53TLXR4",
8   "featuredEvent":"MCZOCY2AM5PFBADN5UDRB53TLXR4",
9   "excerpt":"this is test except",
10   "body":"&lt;p&gt;Test body&lt;/p&gt;"
11   }
12}

Properties

Name	Type	Description	Required or Optional	Available Version
`contentBody`	Map<String, Object>	Body of the managed content.	Required	54.0
`contentKey`	String	Content key to assign to the managed content. A content key is a universally unique identifier (UUID) such as MCA4CCV5QS2BAB5H7YRCRPTCWGZQ.	Optional	56.0
`contentSpaceOrFolderId`	String	Content space or folder ID where the content is created.	Required	54.0
`contentType`	String	Fully qualified name of the content type to create. If you’re uploading a binary file using a multipart/form-data message, `contentType` must be `sfdc_cms__image` or `sfdc_cms__doc`.	Required	54.0
`externalId`	String	External ID of the managed content.	Optional	58.0
`title`	String	Title of the managed content.	Required	54.0
`urlName`	String	URL name of the managed content within the org.	Optional	54.0

Response body for POST

Managed Content Document

Connect REST API Developer Guide

CMS Contents