Answer an invitation
events_respondDestructive
Accept, tentatively accept or decline an invitation - an RSVP of yes, maybe or no; the account's provider sends the answer, with message where given, to its organiser from the account's own address unless notify is none. Answering a whole series answers each occurrence answered apart from it too, and says under replaced how many of their answers it replaced. In a calendar connected by its server's password, the server sends it where it says it sends answers itself - every time and with no message, so a call there naming a message or notify other than all is refused - and the answer is refused where it says no such thing. An invitation in an iCloud calendar is answered from its invitation letter or in Apple's own Calendar app, never here.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| scope | No | For an occurrence of a recurring series: occurrence, where omitted, acts on that occurrence alone, series on its whole series. A series named by its own seriesId is refused unless series is passed. | |
| notify | No | Whether the organiser is told: all where omitted, none to answer untold; on Google, externalOnly tells an organiser outside Google Calendar alone. | |
| account | Yes | The connected account, by the address calendars_list names. | |
| eventId | Yes | The event's id, as events_list names it. | |
| message | No | Words sent to the organiser with the answer; on Google every guest of the event can read them too. | |
| provider | No | The account's provider, as calendars_list names it; needed only where two connected accounts share an address. | |
| response | Yes | ||
| calendarId | No | The calendar holding the event, by the calendarId events_list names; a Google account's event outside its default calendar needs it. |