/mcpThe following is the response from the above GET request and the actual response will depend upon the information given by you: { "@total": "1", "SubscriberDependency": { "DependencyType": "Standard Greeting", "DependentEntityObjectId": "7ea0ecb6-4125-4866-a0f6-5308a5a4b3d1", "DependentEntityObjectType": "66", "DependentEntityOwner": "Texoma_SystemCallhandlerTemplate_1", "DependencyDestinationType": "0", "SubscriberObjectId": "4bc6f97a-0c97-4ed9-a7e2-05e611bb02d3", "UserURI": "/vmrest/users/4bc6f97a-0c97-4ed9-a7e2-05e611bb02d3", "DependentEntityOwnerType": "Call Handler Template" } } Response Code: 200 Finding Dependencies Example 1: Suppose following is the dependent object of a particular user and it is required to find the complete dependency, then below are the steps that should be followed. Dependent Object: <SubscriberDependency> <DependencyType>Standard Greeting</DependencyType> <DependentEntityObjectId>7ea0ecb6-4125-4866-a0f6-5308a5a4b3d1</DependentEntityObjectId> <DependentEntityObjectType>66</DependentEntityObjectType> <DependentEntityOwner>Texoma_SystemCallhandlerTemplate_1 </DependentEntityOwner> <DependencyDestinationType>0</DependencyDestinationType> <SubscriberObjectId>4bc6f97a-0c97-4ed9-a7e2-05e611bb02d3</SubscriberObjectId> <UserURI>/vmrest/users/4bc6f97a-0c97-4ed9-a7e2-05e611bb02d3</UserURI> <DependentEntityOwnerType>Call Handler Template</DependentEntityOwnerType> </SubscriberDependency> Steps to be followed: • Check DependentEntityOwnerType and DependentEntityObjectId from the response, which depicts the type of object referencing the user. In the example, the referencing object entity is call handler template, whose name is 'Texoma_SystemCallhandlerTemplate_1' and object id is '7ea0ecb6-4125-4866-a0f6-5308a5a4b3d1'. • Check DependencyType, which specifies type of dependency. In this example, it is Standard Greeting. For more information, see the Possible Value of DependencyType section. • Check DependencyDestinationType, where user is actually referred. In the example, it is 0 that is After Greeting Action. For more information, see the Possible Values of DependencyDestinationType section. • Therefore, user is referenced in the After Greeting action of Standard Greeting of callhandler template(Texoma_SystemCallhandlerTemplate_1) Example 2: Dependent Object: <SubscriberDependency> <DependencyType>PCTRCaller</DependencyType> <DependentEntityObjectId>476dd400-4130-4795-9e15-c8ce3dd57ff3</DependentEntityObjectId> <DependentEntityObjectType>45</DependentEntityObjectType> <DependentEntityOwner>Donald_Operator_1</DependentEntityOwner> <DependencyDestinationType>4</DependencyDestinationType> Cisco Unity Connection Provisioning Interface (CUPI) API 23 Cisco Unity Connection Provisioning Interface (CUPI) API -- Subscriber Dependency Finding Dependencies