Update event
teamup_update_eventDestructiveIdempotent
WRITE: change fields of an event; fields you leave out keep their value (the event is read first and sent back with its version, so a concurrent edit is refused instead of overwritten; an event without a version is not changed). Needs modify permission. For a recurring event pass redit; use the occurrence id (123-rid-) with single or future. Attachments are not touched. The reply holds the event and an undo_id for one hour (teamup_undo_event_action). PUT /{calendarKey}/events/{id}.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| end | No | New end. | |
| who | No | ||
| notes | No | New notes, in markdown. Replaces the old notes. | |
| redit | No | Which occurrences of a recurring event: single (only this one), future (this and all later ones) or all. | |
| rrule | No | New recurrence rule; with redit all or future only. An empty string removes the recurrence (the series becomes a single event). | |
| start | No | New start (same formats as in teamup_create_event). | |
| title | No | ||
| custom | No | Custom field values to set, keyed by field id; other custom fields keep their value. | |
| all_day | No | ||
| event_id | Yes | Event id (occurrence id for one occurrence of a recurring event). | |
| location | No | ||
| signup_limit | No | ||
| signup_enabled | No | ||
| subcalendar_ids | No | Sub-calendar ids the event belongs to (from teamup_list_subcalendars). | |
| comments_enabled | No | ||
| signup_visibility | No | ||
| comments_visibility | No |