CdmChangesetsApi

"cdm_application": {
  "link": "String",
  "value": "String"
}

"committed_by": {
  "link": "String",
  "value": "String"
}

"error": {
  "detail": "String",
  "message": "String"
}

</td></tr><tr><td>

changeset\_id.link

</td><td>

Query to use to call the Table REST endpoint to retrieve the associated changeset.Data type: String

</td></tr><tr><td>

changeset\_id.value

</td><td>

Sys\_id of the associated changeset.Data type: String

Table: CDM Changeset \[sn\_cdm\_changeset\]

</td></tr><tr><td>

conflict

</td><td>

Flag that indicates whether there is a conflict in the associated changeset.Valid values:

-   true: Conflict detected.
-   false: No conflict found.

Data type: Boolean

</td></tr><tr><td>

created

</td><td>

Date and time when the node was created.Format: YYYY-mm-DD hh:mm:ss

Data type: String

</td></tr><tr><td>

created\_by

</td><td>

User name of the user that create the node. For example, able.tuter.Data type: String

</td></tr><tr><td>

error

</td><td>

If an error occurred during processing, the details about the error.Data type: Object

</td></tr><tr><td>

error.detail

</td><td>

Additional information about the error.Data type: String

</td></tr><tr><td>

error.message

</td><td>

Error message that was generated while trying to process the request.Data type: String

</td></tr><tr><td>

name\_path

</td><td>

Node path name.Data type: String

</td></tr><tr><td>

new\_name

</td><td>

Current name of the node.Data type: String

</td></tr><tr><td>

new\_value

</td><td>

Current value of the node. For leaf nodes and array literals.Data type: String

</td></tr><tr><td>

old\_name

</td><td>

Previous name of the node.Data type: String

</td></tr><tr><td>

old\_value

</td><td>

Previous value of the node. For leaf nodes and array literals.Data type: String

</td></tr><tr><td>

updated

</td><td>

Date and time when the node was last updated.Format: YYYY-mm-DD hh:mm:ss

Data type: String

</td></tr><tr><td>

updated\_by

</td><td>

User name of the user that last updated the node. For example, able.tuter.Data type: String

</td></tr><tr><td>

secure

</td><td>

Flag that indicates whether the associated leaf node was secured.Valid values:

-   true: Node was secured.
-   false: Node was not secured.

Data type: Boolean

</td></tr><tr><td>

type

</td><td>

Node type.

Possible values:

-   sn\_cdm\_node\_collection
-   sn\_cdm\_node\_component
-   sn\_cdm\_node\_folder
-   sn\_cdm\_node\_cdi
-   sn\_cdm\_node\_variable

Data type: String

</td></tr></tbody>
</table>

### cURL request

This code example shows how to retrieve the node changes for a specific changeset.

Return results:

## CdmChangesetsApi - GET /sn\_cdm/changesets/commit-status/\{commit\_id\}

Returns the current status of the specified changeset commit request.

### URL format

Versioned URL: `/api/sn_cdm/{api_version}/changesets/commit-status/{commit_id}`

Default URL: `/api/sn_cdm/changesets/commit-status/{commit_id}`

**Note:** Available versions are specified in the [REST API Explorer](../rest-api-explorer/use-REST-API-Explorer.md). For scripted REST APIs there is additional version information on the [Scripted REST Service form](../rest-api-explorer/c_CustomWebServices.md).

### Supported request parameters

<table class="rest_api_path_parameters"><thead><tr><th>

Name

</th><th>

Description

</th></tr></thead><tbody><tr><td>

api\_version

</td><td id="version-entry-RESTAPI">

Optional. Version of the endpoint to access. For example, `v1` or `v2`. Only specify this value to use an endpoint version other than the latest. Data type: String

</td></tr><tr><td>

commit\_id

</td><td>

Sys\_id for the commit request whose status to return. This value is returned by the <a href="./">CdmChangesetsApi - POST /sn_cdm/changesets/\{changeset_id\}/commit</a> endpoint.

Data type: String

</td></tr></tbody>
</table>

|Name|Description|
|----|-----------|
|None| |

|Name|Description|
|----|-----------|
|None| |

### Headers

The following request and response headers apply to this HTTP action only, or apply to this action in a distinct way. For a list of general headers used in the REST API, see [Supported REST API headers](../rest-api-explorer/c_RESTAPI.md).

|Header|Description|
|------|-----------|
|Accept|Data format of the response body. Only supports **application/json**.|

|Header|Description|
|------|-----------|
|None| |

### Status codes

The following status codes apply to this HTTP action. For a list of possible status codes used in the REST API, see [REST API HTTP response codes](../rest-api-explorer/c_RESTAPI.md).

|Status code|Description|
|-----------|-----------|
|200|Successful. The request was successfully processed.|
|400|Bad Request. A bad request type or malformed request was detected.|
|500|Internal server error. An unexpected error occurred while processing the request. The response contains additional information about the error.|

### Response body parameters

<table><thead><tr><th>

Name

</th><th>

Description

</th></tr></thead><tbody><tr id="cdm_apps-request_id-row"><td>

commit\_id

</td><td>

Commit request record sys\_id. Same as that passed into the endpoint.Data type: String

</td></tr><tr><td>

errors

</td><td>

Description of the error\(s\) encountered during upload.Data type: String

</td></tr><tr><td>

output

</td><td>

Description of the uploaded data or if an error occurred during the upload, an error message describing the error that was encountered.Data type: Object

</td></tr><tr><td>

output.auto\_validate

</td><td>

Indicates whether to invoke validation after the commit.Data type: String

</td></tr><tr><td>

output.cdm\_application

</td><td>

Name of application under which the upload was performed.Data type: String

</td></tr><tr><td>

output.committed\_at

</td><td>

Date and time that the uploaded content was committed.Data type: String

</td></tr><tr><td>

output.committed\_by

</td><td>

Sys\_id of the record of the entity that performed the commit.Data type: String

</td></tr><tr><td>

output.description

</td><td>

Not currently used.Data type: String

</td></tr><tr><td>

output.last\_conflict\_detection\_time

</td><td>

Date and time conflict detection invocation.Data type: String

</td></tr><tr><td>

output.number

</td><td>

Unique number of the changeset.Data type: String

</td></tr><tr><td>

output.publish\_option

</td><td>

Publish option for the associated configured snapshots.

Valid values:

-   publish\_none: Don't publish any snapshots.
-   publish\_valid: Publish only those snapshots that pass validation after the commit.

For additional information on publishing snapshots, see <a href="../../../it-service-management/devops-family/cdm-snapshot-publish/">Publish or unpublish a snapshot</a>.

Data type: String

Default: publish\_none

</td></tr><tr><td>

output.snapshot\_description

</td><td>

Description of the associated snapshot.Data type: String

</td></tr><tr><td>

output.snapshot\_name

</td><td>

Name of the associated snapshot.Data type: String

</td></tr><tr><td>

output.state

</td><td>

State of the upload content.Possible values:

-   committed
-   completed
-   error
-   in\_progress
-   new
-   ready

Data type: String

</td></tr><tr><td>

output.sys\_created\_by

</td><td>

Sys\_id of the entity that created the record.Data type: String

</td></tr><tr><td>

output.sys\_id

</td><td>

Sys\_id of the record containing the changeset.Data type: String

</td></tr><tr><td>

output.title

</td><td>

Title of changeset created as part of the upload.Data type: String

</td></tr><tr><td>

processing\_state

</td><td>

Current processing state of the commit request.Possible values:

-   NOT\_PROCREED
-   PROCESSED

Data type: String

</td></tr><tr id="cdm_apps-export_id-row"><td>

request\_id

</td><td>Request ID. Same as that passed into the endpoint and <strong>commit_id</strong>.Data type: String</td></tr><tr id="cdm_apps-state-row"><td>

state

</td><td>

Current state of the specified commit.Possible values:

-   completed
-   error
-   in\_progress
-   new
-   ready

Data type: String

Table: Value from state column of the CDM Request Queue \[sn\_cdm\_request\_queue\] table.

</td></tr><tr><td>

type

</td><td>

Type of request.Possible values:

-   commit
-   export
-   upload\_and\_commit

Data type: String

</td></tr></tbody>
</table>

### cURL request

The following example shows how to call this endpoint to obtain the status of the specified commit.

The following shows examples of a success and error response.

## CdmChangesetsApi - GET /sn\_cdm/changesets/impacted-deployables

Returns the list of deployables that are associated with a specified changeset.

The CDM Viewer role is required to access this endpoint.

### URL format

Versioned URL: `/api/sn_cdm/{api_version}/changesets/impacted-deployables`

Default URL: `/api/sn_cdm/changesets/impacted-deployables`

**Note:** Available versions are specified in the [REST API Explorer](../rest-api-explorer/use-REST-API-Explorer.md). For scripted REST APIs there is additional version information on the [Scripted REST Service form](../rest-api-explorer/c_CustomWebServices.md).

### Supported request parameters

<table class="rest_api_path_parameters"><thead><tr><th>

Name

</th><th>

Description

</th></tr></thead><tbody><tr><td>

api\_version

</td><td id="version-entry-RESTAPI">

Optional. Version of the endpoint to access. For example, `v1` or `v2`. Only specify this value to use an endpoint version other than the latest. Data type: String

</td></tr></tbody>
</table>

<table class="rest_api_query_parameters"><thead><tr><th>

Name

</th><th>

Description

</th></tr></thead><tbody><tr><td>

changesetNumber

</td><td id="changesetNumber-changeset-entry">

Required. Unique identifier of the associated changeset, such as "Chset-10".

Data type: String

Table: CDM Changeset \[sn\_cdm\_changeset\]

</td></tr><tr><td>

returnFields

</td><td id="cdm_apps-returnFields-entry">

List of fields to return as part of the response. Pass the record column names such as sys\_id, sys\_updated\_by, or state.Data type: Array

Default: All fields as determined by the endpoint

</td></tr></tbody>
</table>

|Name|Description|
|----|-----------|
|None| |

### Headers

The following request and response headers apply to this HTTP action only, or apply to this action in a distinct way. For a list of general headers used in the REST API, see [Supported REST API headers](../rest-api-explorer/c_RESTAPI.md).

|Header|Description|
|------|-----------|
|Accept|Data format of the response body. Only supports **application/json**.|

|Header|Description|
|------|-----------|
|None| |

### Status codes

The following status codes apply to this HTTP action. For a list of possible status codes used in the REST API, see [REST API HTTP response codes](../rest-api-explorer/c_RESTAPI.md).

|Status code|Description|
|-----------|-----------|
|200|Successful. The request was successfully processed.|
|400|Bad Request. A bad request type or malformed request was detected.|
|500|Internal server error. An unexpected error occurred while processing the request. The response contains additional information about the error.|

### Response body parameters

<table id="id_lcm_5dn_qtb"><thead><tr><th>

Name

</th><th>

Description

</th></tr></thead><tbody><tr><td>

cdi\_count

</td><td>

Number of configuration data items \(CDIs\) contained in the associated CDM application.Data type: Number \(Integer\)

</td></tr><tr><td>

cdi\_usage

</td><td>

Percentage of the CDIs used by the deployable.Data type: Number \(Integer\)

</td></tr><tr><td>

cdm\_app

</td><td>

CDM application object associated with the deployable.Data type: Object

</td></tr><tr><td>

cdm\_app.link

</td><td id="cdm_app_link-app-entry">

Call to use to access the CDM application record using the REST Table API. Data type: String

</td></tr><tr><td>

cdm\_app.value

</td><td id="cdm_app_value-app-entry">

Sys\_id of the associated CDM application record.Data type: String

Table: CDM Application \[sn\_cdm\_application\]

</td></tr><tr><td>

cdm\_ci

</td><td>

Application service object associated with the deployable.Data type: Object

</td></tr><tr><td>

cdm\_ci.link

</td><td>

Call to use to access the application service record using the REST Table API.Data type: String

</td></tr><tr><td>

cdm\_ci.value

</td><td>

Sys\_id of the associated application service record. Data type: String

Table: Configuration Item \[cmdb\_ci\]

</td></tr><tr><td>

description

</td><td>

Description of the generated CDM deployable.Data type: String

</td></tr><tr><td>

environment\_type

</td><td>

Environment type of the deployable.Possible values:

-   Development
-   Production
-   Test

Data type: String

</td></tr><tr><td>

error

</td><td id="cdm_apps-error-entry">

Only returned if an error occurred during processing.Data type: Object

</td></tr><tr><td>

error.detail

</td><td>

Additional information about the error.Data type: String

</td></tr><tr><td>

error.message

</td><td>

Error message that was generated while trying to process the request.Data type: String

</td></tr><tr><td>

name

</td><td>

Name of the CDM deployable.Data type: String

</td></tr><tr><td>

node

</td><td>

Details about the deployable node.Data type: Object

</td></tr><tr><td>

node.link

</td><td>

Call to use to access the deployable node record using the REST Table API. Data type: String

</td></tr><tr><td>

node.value

</td><td>

Sys\_id of the deployable node record.Data type: String

Table: CDM Deployable \[sn\_cdm\_deployable\]

</td></tr><tr><td>

snapshot\_version\_counter

</td><td>

Number of snapshots created for the deployable.Data type: Number \(Integer\)

</td></tr><tr><td>

state

</td><td>

Current state of the deployable.Possible values:

-   active
-   deleted

Data type: String

</td></tr><tr id="cdm_dep-sys_created_by-row"><td>

sys\_created\_by

</td><td>

User name of the user that created the CDM deployable. For example, able.tuter.Data type: String

</td></tr><tr id="cdm_deps-sys_created_on-row"><td>

sys\_created\_on

</td><td>

Date and time when the CDM deployable was created.Data type: String

Format: YYYY-mm-DD hh:mm:ss

</td></tr><tr><td>

sys\_id

</td><td>

Sys\_id of the created deployable.Data type: String

Table: CDM Deployable \[sn\_cdm\_deployable\]

</td></tr><tr id="cdm_dep-sys_updated_by-row"><td>

sys\_updated\_by

</td><td>

User name of the user that last updated the CDM deployable. For example, able.tuter.Data type: String

</td></tr><tr id="cdm_dep-sys_updated_on-row"><td>

sys\_updated\_on

</td><td>

Date and time when the CDM deployable was last updated.Data type: String

Format: YYYY-mm-DD hh:mm:ss

</td></tr></tbody>
</table>

### cURL request

The following code example shows how to retrieve the impacted deployables for a specified changeset.

Return results:

## CdmChangesetsApi - GET /sn\_cdm/changesets/impacted-shared-components

Returns a list of shared components that are associated with a specified changeset.

The CDM Viewer role is required to access this endpoint.

### URL format

Versioned URL: `/api/sn_cdm/{api_version}/changesets/impacted-shared-components`

Default URL: `/api/sn_cdm/changesets/impacted-shared-components`

**Note:** Available versions are specified in the [REST API Explorer](../rest-api-explorer/use-REST-API-Explorer.md). For scripted REST APIs there is additional version information on the [Scripted REST Service form](../rest-api-explorer/c_CustomWebServices.md).

### Supported request parameters

<table class="rest_api_path_parameters"><thead><tr><th>

Name

</th><th>

Description

</th></tr></thead><tbody><tr><td>

api\_version

</td><td id="version-entry-RESTAPI">

Optional. Version of the endpoint to access. For example, `v1` or `v2`. Only specify this value to use an endpoint version other than the latest. Data type: String

</td></tr></tbody>
</table>

<table class="rest_api_query_parameters"><thead><tr><th>

Name

</th><th>

Description

</th></tr></thead><tbody><tr><td>

changesetNumber

</td><td id="changesetNumber-changeset-entry">

Required. Unique identifier of the associated changeset, such as "Chset-10".

Data type: String

Table: CDM Changeset \[sn\_cdm\_changeset\]

</td></tr><tr><td>

returnFields

</td><td id="cdm_apps-returnFields-entry">

List of fields to return as part of the response. Pass the record column names such as sys\_id, sys\_updated\_by, or state.Data type: Array

Default: All fields as determined by the endpoint

</td></tr></tbody>
</table>

|Name|Description|
|----|-----------|
|None| |

### Headers

The following request and response headers apply to this HTTP action only, or apply to this action in a distinct way. For a list of general headers used in the REST API, see [Supported REST API headers](../rest-api-explorer/c_RESTAPI.md).

|Header|Description|
|------|-----------|
|Accept|Data format of the response body. Only supports **application/json**.|

|Header|Description|
|------|-----------|
|None| |

### Status codes

The following status codes apply to this HTTP action. For a list of possible status codes used in the REST API, see [REST API HTTP response codes](../rest-api-explorer/c_RESTAPI.md).

|Status code|Description|
|-----------|-----------|
|200|Successful. The request was successfully processed.|
|400|Bad Request. The passed changeset does not exist.|
|500|Internal server error. An unexpected error occurred while processing the request. The response contains additional information about the error.|

### Response body parameters

<table><thead><tr><th>

Name

</th><th>

Description

</th></tr></thead><tbody><tr><td>

cdm\_shared\_\_library

</td><td>

Sys\_id of the shared library under which the component resides.Data type: String

</td></tr><tr><td>

description

</td><td>

Description of the CDM shared component.Data type: String

</td></tr><tr><td>

error

</td><td id="cdm_apps-error-entry">

Only returned if an error occurred during processing.Data type: Object

</td></tr><tr><td>

error.detail

</td><td id="cdm_apps-error_detail-entry">

Details about the error that occurred.Data type: String

</td></tr><tr><td>

error.message

</td><td id="cdm_apps-error_message-entry">

Message that provides an overview of the error.Data type: String

</td></tr><tr><td>

name

</td><td>

Name of the CDM shared component.Data type: String

</td></tr><tr><td>

node

</td><td>

Sys\_id of the shared component node.Data type: String

Table: CDM Node \[sn\_cdm\_node\]

</td></tr><tr><td>

node\_main

</td><td>

Sys\_id of the main\_id of the shared component node record.Data type: String

Table: CDM Node Main \[sn\_cdm\_node\_main\]

</td></tr><tr><td>

state

</td><td>

Current state of the shared component.Possible values:

-   active
-   deleted

Data type: String

</td></tr><tr id="cdm_dep-sys_created_by-row"><td>

sys\_created\_by

</td><td>

User name of the user that create the CDM shared component. For example, able.tuter.Data type: String

</td></tr><tr id="cdm_deps-sys_created_on-row"><td>

sys\_created\_on

</td><td>

Date and time when the CDM shared component was created.Format: YYYY-mm-DD hh:mm:ss

Data type: String

</td></tr><tr><td>

sys\_id

</td><td>

Sys\_id of the shared component.Data type: String

Table: CDM Shared Component \[sn\_cdm\_shared\_component\]

</td></tr><tr id="cdm_dep-sys_updated_by-row"><td>

sys\_updated\_by

</td><td>

User name of the user that last updated the CDM shared component. For example, able.tuter.Data type: String

</td></tr><tr id="cdm_dep-sys_updated_on-row"><td>

sys\_updated\_on

</td><td>

Date and time when the CDM shared component was last updated.Format: YYYY-mm-DD hh:mm:ss

 Data type: String

</td></tr><tr><td>

version\_counter

</td><td>

Number of versions created for the shared component.Data type: Integer

</td></tr></tbody>
</table>

### cURL request

The following code example shows how to retrieve the impacted shared components for changeset = "Chset-20".

Response:

## CdmChangesetsApi - GET /sn\_cdm/changesets/\{changeset\_id\}/impacted-deployables

Returns the list of deployables that are associated with a specified changeset.

### URL format

Versioned URL: `/api/sn_cdm/{api_version}/changesets/{changeset_id}/impacted-deployables`

Default URL: `/api/sn_cdm/changesets/{changeset_id}/impacted-deployables`

**Note:** Available versions are specified in the [REST API Explorer](../rest-api-explorer/use-REST-API-Explorer.md). For scripted REST APIs there is additional version information on the [Scripted REST Service form](../rest-api-explorer/c_CustomWebServices.md).

### Supported request parameters

<table class="rest_api_path_parameters"><thead><tr><th>

Name

</th><th>

Description

</th></tr></thead><tbody><tr><td>

api\_version

</td><td id="version-entry-RESTAPI">

Optional. Version of the endpoint to access. For example, `v1` or `v2`. Only specify this value to use an endpoint version other than the latest. Data type: String

</td></tr><tr><td>

changeset\_id

</td><td>

Sys\_id of the changeset record to process.Data type: String

Table:CDM Changeset \[sn\_cdm\_changeset\]

</td></tr></tbody>
</table>

|Name|Description|
|----|-----------|
|None| |

|Name|Description|
|----|-----------|
|None| |

### Headers

The following request and response headers apply to this HTTP action only, or apply to this action in a distinct way. For a list of general headers used in the REST API, see [Supported REST API headers](../rest-api-explorer/c_RESTAPI.md).

|Header|Description|
|------|-----------|
|Accept|Data format of the response body. Only supports **application/json**.|

|Header|Description|
|------|-----------|
|None| |

### Status codes

The following status codes apply to this HTTP action. For a list of possible status codes used in the REST API, see [REST API HTTP response codes](../rest-api-explorer/c_RESTAPI.md).

|Status code|Description|
|-----------|-----------|
|200|Successful. The request was successfully processed.|
|400|Bad Request. A bad request type or malformed request was detected.|
|500|Internal server error. An unexpected error occurred while processing the request. The response contains additional information about the error.|

### Response body parameters

<table><thead><tr><th>

Name

</th><th>

Description

</th></tr></thead><tbody><tr><td>

changeset\_id

</td><td>

Sys\_id of the last changeset associated with the deployable node.Data type: String

</td></tr><tr><td>

conflict

</td><td><p>Flag that indicates whether the associated deployable is in conflict.Possible values:</p>
<ul>
<li>0: Not in conflict.</li>
<li>1: Conflicted - refer to the <strong>conflict_type</strong> return result for additional information.</li>
</ul>
<p>Data type: Number</p></td></tr><tr><td>

conflict\_type

</td><td>

Type of deployable conflict.Possible values:

-   corrupted\_node
-   deleted\_node
-   duplicated\_node
-   incomplete\_deleted\_parent
-   incomplete\_deleted\_ref
-   incomplete\_renamed\_ref
-   invalid\_include
-   orphaned\_descendant
-   related\_conflict
-   unlinked\_include
-   unrenamed\_include
-   updated\_node

Data type: String

</td></tr><tr><td>

description

</td><td>

Description of the deployable node.Data type: String

</td></tr><tr><td>

effective\_from

</td><td>

Timestamp when the node is valid. This value is `null` until you commit a changeset in which the node was created.Data type: Number

</td></tr><tr><td>

effective\_to

</td><td>

Timestamp when the node is no longer valid. If this value is `null`, the node stays in affect until it is replaced with a new version.Data type: Number

</td></tr><tr><td>

error

</td><td>

If an error occurred during processing, the details about the error.Data type: Object

</td></tr><tr><td>

error.detail

</td><td>

Additional information about the error.Data type: String

</td></tr><tr><td>

error.message

</td><td>

Error message that was generated while trying to process the request.Data type: String

</td></tr><tr><td>

level

</td><td>

Depth of the node starting from the application level, which is 0.Data type: Number

</td></tr><tr><td>

linked\_to

</td><td><p>ID of the reference node within a collection and component.For example, the following node snippet shows a link between the collection collA and the component compA. For this example, the <strong>linkedTo</strong> value is <code>1</code>:</p>
<div class="highlight"><pre><span></span><code>{ 
components : {compA:{} //MainId: 1}, 

Collections : { collA : {  
   compA :{} //Include, linkedTo: 1 
    } 
  } 
} 
</code></pre></div>
<p>Data type: String</p></td></tr><tr><td>

main\_id

</td><td>

Unique identifier of the deployable node. This value is generated when the node is created and used to identify the deployable node.Data type: Number

</td></tr><tr><td>

main\_id\_encoded

</td><td>Encoded value of the <strong>mainId</strong> return results, using Radix 57 string representation.Data type: String</td></tr><tr><td>

name

</td><td>

Name of the deployable.Data type: String

</td></tr><tr><td>

node\_classifier

</td><td>

Node classification, such as Development, Production, or Test. In the format:

-   /application/deployables/env:Development
-   /application/deployables/env:Production
-   /application/deployables/env:Test

Data type: String

</td></tr><tr><td>

position

</td><td>

Deployable node position. Only applicable to arrays.For example, for the array:

\{\} is position 1000,

"literal1" is position 2000,

"literal2" is position 3000,

\[\] is position 4000

Data type: Number

</td></tr><tr><td>

previous\_version

</td><td>

Sys\_id of the previous version of the associated deployable node.Data type: String

</td></tr><tr><td>

restricted\_to

</td><td>

List of sys\_ids of the users that are allowed to access the associated deployable node. This value is `null` if all groups can access the deployable.Data type: String

Table: CDM Restricted Groups \[sn\_cdm\_restricted\_groups\]

</td></tr><tr><td>

secure\_value

</td><td>Secure value of the CDI or variable. Only returned for leaf nodes and array literals. This is the same as the <strong>value</strong> return result, but is encrypted.Data type: String</td></tr><tr><td>

status

</td><td>

Status of deployable node or the status of a failed request.Possible values:

-   deleted
-   failure \(passed if endpoint call fails.\)
-   new
-   superseded
-   updated
-   valid

Data type: String

</td></tr><tr><td>

system\_folder

</td><td>

Flag that indicates whether the associated folder is a system folder.Possible values:

-   0: Not a system folder.
-   1: System folder.

Data type: Number

</td></tr><tr><td>

sys\_id

</td><td>

Sys\_id of the impacted deployable.Data type: String

</td></tr><tr><td>

type

</td><td>

Node type, such as sn\_cdm\_node\_deployable. This value enables you to determine whether the node is a component, config data item \(CDI\), or deployable. This value is generated when the node is created.Data type: String

</td></tr><tr><td>

value

</td><td><p>Value of the CDI or variable. Only returned for leaf nodes and array literals. If this information is encrypted, it is returned in the <strong>secure_value</strong> return result.For example, if this node is the CDI <code>nodeA:{cdi1: 1}</code>, the <strong>value</strong> return result is <code>1</code>. If it is an array node such as <code>node1: {arrayNode: [{}, "literal1", "literal2", []]}</code>, the <strong>value</strong> return result is <code>literal1</code>.</p>
<p>Data type: String</p></td></tr></tbody>
</table>

### cURL request

The following example shows how to request the deployables that are associated with the changeset whose sys\_id is bf506e69537c3010a1d3ddeeff7b12c0.

The following shows both a successful and an error response for this endpoint.

## CdmChangesetsApi - POST /sn\_cdm/changesets/\{changeset\_id\}/commit

Commits the specified changeset. Once committed, the changeset is persisted into the CDM tables within the associated instance.

The system updates the application to persist the changes to the configuration data within the changeset. The changeset state changes to **Committed**. The system then generates a snapshot of each deployable that is affected by the changeset.

This endpoint returns the ID of the commit request. Use this ID to call the [CdmChangesetsApi - GET /sn\_cdm/changesets/commit-status/\{commit\_id\}](changesets-api.md) endpoint to obtain the current status of the changeset commit.

### URL format

Versioned URL: `/api/sn_cdm/{api_version}/changesets/{changeset_id}/commit`

Default URL: `/api/sn_cdm/changesets/{changeset_id}/commit`

**Note:** Available versions are specified in the [REST API Explorer](../rest-api-explorer/use-REST-API-Explorer.md). For scripted REST APIs there is additional version information on the [Scripted REST Service form](../rest-api-explorer/c_CustomWebServices.md).

### Supported request parameters

<table class="rest_api_path_parameters"><thead><tr><th>

Name

</th><th>

Description

</th></tr></thead><tbody><tr><td>

api\_version

</td><td id="version-entry-RESTAPI">

Optional. Version of the endpoint to access. For example, `v1` or `v2`. Only specify this value to use an endpoint version other than the latest. Data type: String

</td></tr><tr><td>

changeset\_id

</td><td>

Sys\_id of the changeset record to process.Data type: String

Table:CDM Changeset \[sn\_cdm\_changeset\]

</td></tr></tbody>
</table>

<table class="rest_api_query_parameters"><thead><tr><th>

Name

</th><th>

Description

</th></tr></thead><tbody><tr><td>

autoValidate

</td><td>

Flag that indicates whether the snapshots created upon commit are validated, meaning any associated policies are run against the snapshot.Valid values:

-   true: Validate the snapshots.
-   false: Do not validate the snapshots.

Default: false

</td></tr><tr><td>

publishOption

</td><td><p>Publish option for the associated configuration snapshots. Valid values:</p>
<ul>
<li>publish_none: Do not publish any snapshots.</li>
<li>publish_valid: Publish only those snapshots that pass validation after the commit.</li>
</ul>
<p><strong>Note:</strong> This option is only available if the value for the <strong>autoCommit</strong> parameter is true.</p>
<p>For additional information on publishing snapshots, see <a href="../../../it-service-management/devops-family/cdm-snapshot-publish/">Publish or unpublish a snapshot</a>.</p>
<p>Data type: String</p>
<p>Default: publish_none</p></td></tr></tbody>
</table>

|Name|Description|
|----|-----------|
|None| |

### Headers

The following request and response headers apply to this HTTP action only, or apply to this action in a distinct way. For a list of general headers used in the REST API, see [Supported REST API headers](../rest-api-explorer/c_RESTAPI.md).

|Header|Description|
|------|-----------|
|Accept|Data format of the response body. Only supports **application/json**.|
|Content-Type|Data format of the request body. Only supports **application/json**.|

|Header|Description|
|------|-----------|
|None| |

### Status codes

The following status codes apply to this HTTP action. For a list of possible status codes used in the REST API, see [REST API HTTP response codes](../rest-api-explorer/c_RESTAPI.md).

<table><thead><tr><th>

Status code

</th><th>

Description

</th></tr></thead><tbody><tr><td>

200

</td><td id="entry-200-status-code">

Successful. The request was successfully processed.

</td></tr><tr><td>

400

</td><td><p>Bad Request. Error: &lt;Error message&gt;Validate that the <strong>changeset_id</strong> parameter that you passed in was correct.</p>
<p>Ensure that you have the required roles to access this endpoint.</p></td></tr><tr><td>

500

</td><td>Internal Server Error Error: Invalid boolean value.If you passed in the <strong>autoValidate</strong> parameter, verify that it is a boolean value.</td></tr></tbody>
</table>

### Response body parameters

<table id="id_bgt_byy_ztb"><thead><tr><th>

Name

</th><th>

Description

</th></tr></thead><tbody><tr><td>

commit\_id

</td><td>

Sys\_id of the commit request. Use this ID when calling the <a href="./">CdmChangesetsApi - GET /sn_cdm/changesets/commit-status/\{commit_id\}</a> endpoint to check the status of the commit request.

Data type: String

</td></tr><tr><td>

error

</td><td>

If an error occurred during processing, the details about the error.Data type: Object

</td></tr><tr><td>

error.detail

</td><td>

Additional information about the error.Data type: String

</td></tr><tr><td>

error.message

</td><td>

Error message that was generated while trying to process the request.Data type: String

</td></tr><tr><td>

status

</td><td>

Status of the commit. Only returned when an error occurs.Possible values: failure

Data type: String

</td></tr></tbody>
</table>

### cURL request

The following example shows how to call this endpoint to commit a changeset record.

The following shows the response for a successful changeset commit request.

## CdmChangesetsApi - POST /sn\_cdm/changesets/create

Creates a new changeset in the open state for a specified CDM application or shared library.

The CDM Editor role is required to access this endpoint.

### URL format

Versioned URL: `/api/sn_cdm/{api_version}/changesets/create/`

Default URL: `/api/sn_cdm/changesets/create/`

**Note:** Available versions are specified in the [REST API Explorer](../rest-api-explorer/use-REST-API-Explorer.md). For scripted REST APIs there is additional version information on the [Scripted REST Service form](../rest-api-explorer/c_CustomWebServices.md).

### Supported request parameters

<table class="rest_api_path_parameters"><thead><tr><th>

Name

</th><th>

Description

</th></tr></thead><tbody><tr><td>

api\_version

</td><td id="version-entry-RESTAPI">

Optional. Version of the endpoint to access. For example, `v1` or `v2`. Only specify this value to use an endpoint version other than the latest. Data type: String

</td></tr></tbody>
</table>

<table class="rest_api_query_parameters"><thead><tr><th>

Name

</th><th>

Description

</th></tr></thead><tbody><tr><td>

appName

</td><td id="appName-changesets-entry">

Required. Name of the CDM application or shared library to associate with this changeset. This must be an active application or shared library.Data type: String

</td></tr><tr><td>

description

</td><td>

Changeset description. Enter something that will allow others to understand the purpose of the changeset.Data type: String

 Default: None

</td></tr><tr><td>

returnFields

</td><td>

Comma separated list of fields in the CDM Changeset \[sn\_cdm\_changeset\] table to return as part of the response.Data type: String

</td></tr></tbody>
</table>

|Name|Description|
|----|-----------|
|None| |

### Headers

The following request and response headers apply to this HTTP action only, or apply to this action in a distinct way. For a list of general headers used in the REST API, see [Supported REST API headers](../rest-api-explorer/c_RESTAPI.md).

|Header|Description|
|------|-----------|
|Accept|Data format of the response body. Only supports **application/json**.|
|Content-Type|Data format of the request body. Only supports **application/json**.|

|Header|Description|
|------|-----------|
|None| |

### Status codes

The following status codes apply to this HTTP action. For a list of possible status codes used in the REST API, see [REST API HTTP response codes](../rest-api-explorer/c_RESTAPI.md).

<table><thead><tr><th>

Status code

</th><th>

Description

</th></tr></thead><tbody><tr><td>

200

</td><td id="entry-200-status-code">

Successful. The request was successfully processed.

</td></tr><tr><td>

400

</td><td>

Bad Request. Error: &lt;Error message&gt;Ensure that the specified CDM application or shared library exists and in the active state.

</td></tr><tr><td>

500

</td><td id="entry-500-status-code">

Internal server error. An unexpected error occurred while processing the request. The response contains additional information about the error.

</td></tr></tbody>
</table>

### Response body parameters

<table><thead><tr><th>

Name

</th><th>

Description

</th></tr></thead><tbody><tr><td>

auto\_validate

</td><td>

Flag that indicates whether auto validation was performed.

 Possible values:

-   true: Auto validation was performed.
-   false: Auto validation was not preformed.

 Data type: Boolean

</td></tr><tr><td>

cdm\_application

</td><td>

Details about the CDM application associated with the changeset.Data type: Object

 ```
"cdm_application": { 
  "link": "String",
  "value": "String"
}

"error": {
  "detail": "String",
  "message": "String"
}

"error": {
  "detail": "String",
  "message": "String"
}