| Authorization token required | true |
| Admin Authorization token required | false |
<ImportAppointmentsRequest [l="{folder-id}"] ct="{content-type}"> ## ImportAppointmentsRequest
<content [aid="{attachment-upload-id}"] [mid="{message-id}"] [part="{part-identifier}"]>{text}</content> ## ContentSpec
</ImportAppointmentsRequest>
elements and attributes you can define within a
<ImportAppointmentsRequest> element:
| XPath | Required / Optional | Description |
| @l | Optional (0 or 1) | Type: String Optional folder ID to import appointments into |
| @ct | Required (only 1) | Type: String Content type Only currently supported content type is "text/calendar" (and its nickname "ics") |
| /content | Required (only 1) | Type: {text} Content specification Description for element text content:Inlined content data. Ignored if "aid" or "mid"/"part" specified |
| /content@aid | Optional (0 or 1) | Type: String Attachment upload ID of uploaded object to use |
| /content@mid | Optional (0 or 1) | Type: String Message ID of existing message. Used in conjunction with "part" |
| /content@part | Optional (0 or 1) | Type: String Part identifier. This combined with "mid" identifies a part of an existing message |
<ImportAppointmentsResponse ids="{list-of-created-ids}" n="{num-imported} (int)" /> ## ImportAppointmentsResponse
elements and attributes you can define within a
<ImportAppointmentsResponse> element:
| XPath | Required / Optional | Description |
| @ids | Required (only 1) | Type: String List of created IDs |
| @n | Required (only 1) | Type: int Number of imported appointments |