/mcpRetrieving a Schedule To retrieve a single Schedule, an administrator makes a GET to the schedules resource, specifying the Objectid of the requested Schedule in the URI: GET /vmrest/schedules/387f051e-3367-4cc8-abed-810293d39f76 This would return the following on success: 200 OK <?xml version="1.0" encoding="UTF-8"?> <Schedule> <URI>/vmrest/schedules/387f051e-3367-4cc8-abed-810293d39f76</URI> <ObjectId>387f051e-3367-4cc8-abed-810293d39f76</ObjectId> <DisplayName>Weekdays</DisplayName> <OwnerLocationObjectId>6a56503e-c1c8-406c-85fd-76be40994d39</OwnerLocationObjectId> <OwnerLocationURI>/vmrest/locations/connectionlocations/6a56503e-c1c8-406c-85fd-76be40994d39</OwnerLocationURI> <Undeletable>true</Undeletable> <IsHoliday>false</IsHoliday> <ScheduleDetailsURI>/vmrest/schedules/387f051e-3367-4cc8-abed-810293d39f76/scheduledetails</ScheduleDetailsURI> </Schedule> This would return the following if the specified Schedule does not exist: 404 Not Found <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <ErrorDetails> <errors> <code>NOT_FOUND</code> <message>schedule - ObjectId=387f051e-3367-4cc8-abed-810293d39f76</message> </errors> </ErrorDetails> Adding a Schedule To add a new Schedule, an administrator makes a POST to the schedules resource, specifying the new Schedule via XML: POST /vmrest/schedules <Schedule> <DisplayName>EveningShift</DisplayName> <OwnerLocationObjectId>6a56503e-c1c8-406c-85fd-76be40994d39</OwnerLocationObjectId> <IsHoliday>false</IsHoliday> </Schedule> This will return the URI to the newly created Schedule (which includes its ObjectId): 201 Created /vmrest/user/schedules/df7faf3b-3278-4852-b488-7e3134dc3336 Cisco Unity Connection Provisioning Interface (CUPI) API 720 Cisco Unity Connection Provisioning Interface (CUPI) API for Schedules Retrieving a Schedule