![]() ![]() " accepted" - The attendee has accepted the invitation." tentative" - The attendee has tentatively accepted the invitation." declined" - The attendee has declined the invitation." needsAction" - The attendee has not responded to the invitation (recommended for new events).Can only be set when the attendee is added to the event for the first time. Whether the attendee is the organizer of the event. It must be a valid email address as per RFC5322. This field must be present when adding an attendee. The attendee's email address, if available. Service accounts need to use domain-wide delegation of authority to populate the attendee list. ![]() See the Events with attendees guide for more information on scheduling events with other calendar users. When updating an event, this can be used to only update the participant's response. When retrieving an event, this may be due to a restriction specified by the maxAttendee query parameter. Whether attendees may have been omitted from the event's representation. Internet media type (MIME type) of the attachment. This field can only be modified for custom third-party attachments. There can be at most 25 attachments per event,įor Google Drive files, this is the ID of the corresponding Files resource entry in the Drive API.įor adding Google Drive file attachments use the same format as in alternateLink property of the Files resource in the Drive API. In order to modify attachments the supportsAttachments request parameter should be set to true. Whether anyone can invite themselves to the event (deprecated). ![]() The Calendar API provides different flavors of event resources, more information can be found in About events.įor a list of methods for this resource, see the end of this page. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |