/mcp<xs:element name="IsDeleted" type="xs:long" minOccurs="0" /> <xs:element name="IsSent" type="xs:long" minOccurs="0" /> <xs:element name="IsFuture" type="xs:long" minOccurs="0" /> <xs:element name="FolderURI" type="xs:anyURI" minOccurs="0" /> </xs:all> </xs:complexType> <xs:element name="Message" type="Message" /> <xs:element name="Messages"> xs:complexType xs:sequence <xs:element name="Message" type="Message" maxOccurs="unbounded" /> </xs:sequence> </xs:complexType> </xs:element> When sending a message, the following fields can be set: • dispatch • secure • priority • sensitivity • read receipt requested • delivery receipt requested • future delivery attribute On a received message, the following fields can be modified: • priority • subject • read Although a message can appear in a folder, it is always available via a unique id: /vmrest/mailbox/messageid Because messages include attachments and recipients that are not efficiently included in the envelope of the message, they are filled out only when an individual message is requested. The following is the resource definition for attachments and recipients: <xs:complexType name="Attachment"> xs:all <xs:element name="URI" type="xs:anyURI" /> </xs:all> </xs:complexType> <xs:element name="Attachment" type="Attachment" /> <xs:complexType name="Attachments"> xs:sequence <xs:element name="Attachment" type="Attachment" maxOccurs="unbounded" /> </xs:sequence> </xs:complexType> Cisco Unity Connection Messaging Interface (CUMI) API 16 Cisco Unity Connection Messaging Interface (CUMI) API -- Using the CUMI API for Sending Messages Sending Messages