/mcpResponse Code: 200 Searching To retrieve a list of Routing Rules that meet a specified search criteria, add the following query parameter to a GET: query=(column [is | startswith] value) For example, to find the Routing Rule at RuleIndex 1: GET https://<connection-server>/vmrest/routingules?query=(RuleIndex%20is%201) Creating The only required field for creating a Routing Rule is DisplayName. All other Routing Rule fields are optional. A Routing Rule that is created with default fields has Type=1 (Direct) and routes to the System Directory Handler. Some examples of other types of Routing Rules can be found at the end of this document. Note that RuleIndex cannot be specified when creating a new Routing Rule; all new Routing Rules are created at RuleIndex 0, and the RuleIndex of all other Routing Rules is incremented by 1 when the new Routing Rule is created. The following is an example of a POST that creates a Routing Rule with the name "My Routing Rule" of Type 1 (Direct): POST https://<connection-server>/vmrest/routingrules <RoutingRule> <DisplayName>My Routing Rule</DisplayName> <Type>1</Type> </RoutingRule> The following is the response from the above POST request: 201 Created /vmrest/routingrules/bd73528d-e810-4533-8aab-89de32013885 JSON Example To create new routing rule, do the following: Request URI: POST https://<connection-server>/vmrest/routingrules Accept: application/json Content-Type: application/json Connection: keep-alive Request Body: { "DisplayName": "Texoma Routing Rule", "Type": "1" } The following is the response from the above POST request and the actual response will depend upon the information given by you: Cisco Unity Connection Provisioning Interface (CUPI) API 569 Cisco Unity Connection Provisioning Interface (CUPI) API--Call Routing Searching