If an entity is a composite entity (as a result of a merge), then each contributor can be unmerged to revert to a standalone entity. For example, the name of the composite entity is Origin and the unmerging entity is Spawn. The difference between the below POST request and the unmerge entity request is in the result. If the Spawn entity was a result of multiple merges, then it is unmerged with all the content contributed in the previous merges. In the case of non-tree unmerge, only the initial state of the Spawn entity is unmerged. The subsequent merges to the Spawn entity are not unmerged.

Request

POST {TenantURL}/<origin id>/_treeUnmerge?contributorURI=<spawn URI>

Table 1. Parameters

Parameter		Required	Description
Headers	Authorization	Yes	Information about authentication access token in format "Bearer <accessToken>" (see details in Authentication API ).
Query	spawnId	Yes	URI of some entity that has been merged into origin and now going to detach from it.
Contributor URI	contributorUri	Yes	URI of contributor need to be unmerged.

Spawn must be the part of Origin at the moment. If it's not, an error will be returned. Parts of actual entities can be seen in the crosswalk tree.