McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 602

↗ View in doc context
page
602
source
unity-connection/rest-api/cupi/cupi.md
chunk_id
unity-connection::rest-api::cupi::cupi::568

Response Code: 201 Updating The following is an example of a PUT request that modifies the DisplayName of an existing Routing Rule: PUT https://<connection-server>/vmrest/routingrules/<objectid> <RoutingRule> <DisplayName>Changed Display Name</DisplayName> </RoutingRule> The following is the response from the above PUT request: 204 No Content Note that the RuleIndex of a Routing Rule cannot be modified with this method. Rather, the ordering of the entire Routing Rules collection can be modified, as described later in this document. JSON Example To update display name of routing rule, do the following: PUT https://<connection-server>/vmrest/routingrules/<routingrulesobjectId> Accept: application/json Content-Type: application/json Connection: keep-alive Request Body { "DisplayName": "Texoma_1 Routing Rule" } The following is the response from the above PUT request and the actual response will depend upon the information given by you: Response Code: 204 Deleting The following is an example of a DELETE request that deletes a Routing Rule: DELETE https://<connection-server>/vmrest/routingrules/<objectid> The following is the response from the above DELETE request: 204 No Content JSON Example DELETE https://<connection-server>/vmrest/routingrules/<routingrulesobjectId> Accept: application/json Connection: keep-alive Cisco Unity Connection Provisioning Interface (CUPI) API 570 Cisco Unity Connection Provisioning Interface (CUPI) API--Call Routing Updating