Create event
teamup_create_eventWRITE: create an event. Needs a calendar key with add or modify permission. Give at least subcalendar_ids, start and end. Not idempotent: a repeated call creates a second event. The reply holds the new event and an undo_id; teamup_undo_event_action removes the event again within one hour. POST /{calendarKey}/events.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| end | Yes | End, same format as start. Must not be before start. | |
| who | No | The "who" field. | |
| notes | No | Notes, in markdown. | |
| rrule | No | Recurrence rule (iCalendar RRULE, e.g. FREQ=WEEKLY;COUNT=10). Omit for a single event. | |
| start | Yes | Start, e.g. 2026-10-14T09:00:00 (calendar timezone) or with an offset such as +02:00. For an all-day event: yyyy-mm-dd. | |
| title | No | Event title. | |
| custom | No | Values of custom fields, keyed by field id (see teamup_get_calendar -> fields). | |
| all_day | No | True for an all-day event (default false). | |
| location | No | ||
| signup_limit | No | Maximum signups; required by Teamup when signup_enabled is true. | |
| signup_enabled | No | Let people sign up (default false). | |
| subcalendar_ids | Yes | Sub-calendar ids the event belongs to (from teamup_list_subcalendars). | |
| comments_enabled | No | Allow comments (default false). | |
| signup_visibility | No | Who sees the signups: all_users or users_with_modify_permission. | |
| comments_visibility | No | Who sees the comments: all_users or users_with_modify_permission. |