McDewey

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

Page 78

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

The following is the response from the PUT request and the actual response will depend upon the information given by you: Response Code: 204 Example 4: Directory handler Request Body: <MenuEntry> <Action>2</Action> <TargetHandlerObjectId>c1fc1029-55f4-40dc-a553-40b75664ed8a</TargetHandlerObjectId> </MenuEntry> The following is the response from the PUT request and the actual response will depend upon the information given by you: Response Code: 204 Example 5: Conversation Request Body: for broadcast message administrator </MenuEntry> <Action>2</Action> <TargetConversation>BroadcastMessageAdministrator</TargetConversation> </MenuEntry> The following is the response from the PUT request for broadcast message administrator and the actual response will depend upon the information given by you: Response Code: 204 Request Body: for caller system transfer <MenuEntry> <Action>2</Action> <TargetConversation>SystemTransfer</TargetConversation> </MenuEntry> The following is the response from the PUT request for caller system transfer and the actual response will depend upon the information given by you: Response Code: 204 Request Body: for greeting administrator <MenuEntry> <Action>2</Action> <TargetConversation>GreetingAdministrator</TargetConversation> </MenuEntry> The following is the response from the PUT request for greeting administrator and the actual response will depend upon the information given by you: Response Code: 204 Request Body: for sign in <MenuEntry> <Action>2</Action> <TargetConversation>SubSignIn</TargetConversation> </MenuEntry> Cisco Unity Connection Provisioning Interface (CUPI) API 46 Cisco Unity Connection Provisioning Interface (CUPI) API -- User Caller Input Updating Caller Input Keys