/mcpPOST /vmrest/users/<user object id>/privatelists <?xml version="1.0" encoding="UTF-8"?> <PrivateList> <DisplayName>2</DisplayName> <VoiceName>6ce746b7-d775-4bc4-9d19-8b6a55b9461d.wav</VoiceName> <NumericId>2</NumericId> </PrivateList> These are the only three parameters that can be explicitly set on a new private list. The other parameters are not allowed on a POST, either defaulting to a certain value or being auto-generated as discussed above. The ObjectId can be explicitly set if desired, but that is optional. Updating Only the following fields can be updated in a PUT request: • DisplayName • VoiceName • NumericId The following example shows a PUT request that modifies some fields, changing a private list to private list 6. PUT /vmrest/users/<user object id>/privatelists/<private list object id> <?xml version="1.0" encoding="UTF-8"?> <PrivateList> <DisplayName>6</DisplayName> <NumericId>6</NumericId> </PrivateList> Deleting A private list can be deleted by a DELETE request: DELETE /vmrest/users/<user object id>/privatelists/<private list object id> Voice Names Creating a voice name for a private list (or for any object exposed in CUPI) is a multi-step process. Step 1: Create a place-holder for the WAV file by doing a POST: POST /vmrest/voicefiles The name of the WAV file will be included in the response. 201 Created 6f9c6d05-42e5-48e3-8d07-204250af320d.wav Step 2: Take the name returned in Step 1, and do a PUT where the HTTP content type is "audio/wav" and the payload content is the audio data: Cisco Unity Connection Provisioning Interface (CUPI) API 216 Cisco Unity Connection Provisioning Interface (CUPI) API for User Account Settings Updating