DXM Access API – Construct a request

Overview

Http verb

Specify one of these HTTP verbs in the request:

• GET - Requests transfer of a current representation of the target resource.
• POST - Requests that the origin server accepts the representation enclosed in the request as data to be processed by the target resource.

Endpoint

A combination of the server that fulfills the request, the web service, and the resource against which the request is being made.

For example, in the POST https://cms.crownpeak.net/<instance_name>/cpt_webservice/accessapi/Asset/Asset_Create

 

Call payload

The call payload is a set of input parameters and attributes that you supply with the request in a JSON or XML formatted request body. API operations have both required and optional inputs.

For example, in the POST /accessapi/Asset/Create, a request body will look like this:

{
  "newName": "Lorem Ipsum",
  "destinationFolderId": 1234,
  "modelId": 5678,
  "type": 2, //Note: type == 2 for asset, 4 for folder
  "templateId": 2312,
  "workflowId": 21,
}

This JSON-formatted request body includes label name, destination folder asset id, model id, type of asset, template id, and workflow id. The information in this request body is used to create a new asset in the CMS.

The list of operations

Access APIs are organized into 29 functional sets. The highlighted below are commonly used when developing custom projects from outside the CMS.

Full documentation for the DXM Access API is available on your instance https://cms.crownpeak.net/<instance_name>/cpt_webservice/swagger/ui/index