Delete recurring meeting
delete_recurring_meetingPermanently delete a recurring meeting series, including its template, schedule, and all occurrences. Requires explicit user confirmation because the action is irreversible.
Instructions
Permanently delete a recurring series: template, schedule, and EVERY occurrence.
Use only on explicit user instruction, and make sure the user means the whole series:
every instantiated meeting of the series — past minutes included — is destroyed with
the template, and when the series has notify set, participants are emailed
cancellations. To drop a single slot instead, cancel_recurring_meeting_occurrence
is the right tool, and delete_meeting removes one instantiated meeting.
Returns a small confirmation object once OpenProject accepts the deletion.
Pitfalls. This needs the 'delete meetings' permission, so a 403 is about the account, not the id. A 404 means the id is wrong, the series was already deleted — or OpenProject before 17.4, which has no recurring-meetings API at all; the hint names all readings.
Cross-references: get_recurring_meeting to check what you are about to destroy;
cancel_recurring_meeting_occurrence for one slot; delete_meeting for one
instantiated meeting.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| confirm | No | Must be true. Ask the user to confirm first — the API offers no undo. Calling with confirm=false returns a confirmation_required error rather than deleting anything. | |
| recurring_meeting_id | Yes | Numeric series id to delete permanently, from list_recurring_meetings. Read it back with get_recurring_meeting first and show the user the title — this removes every occurrence, not one meeting. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Id of the meeting, agenda item, outcome or recurring series that was deleted. | |
| deleted | Yes | True once OpenProject accepted the deletion. | |
| message | Yes | Human-readable confirmation naming what was removed. |