From 866e141e685ca35f63e67b4146865fa22c188cd3 Mon Sep 17 00:00:00 2001
From: Anna Larch <anna@nextcloud.com>
Date: Mon, 31 Oct 2022 13:39:21 +0100
Subject: [PATCH] Document iMIP API change for 26

Signed-off-by: Anna Larch <anna@nextcloud.com>
---
 .../digging_deeper/groupware/calendar.rst     | 21 +++++++++++++++++++
 1 file changed, 21 insertions(+)

diff --git a/developer_manual/digging_deeper/groupware/calendar.rst b/developer_manual/digging_deeper/groupware/calendar.rst
index 91467c837..437e59290 100644
--- a/developer_manual/digging_deeper/groupware/calendar.rst
+++ b/developer_manual/digging_deeper/groupware/calendar.rst
@@ -161,6 +161,27 @@ Calendars that only return `ICalendar` are implicitly read-only. If your app's c
 
     }
 
+Handling iMIP data 
+~~~~~~~~~~~~~~~~~~
+
+You may implement the ``IHandleIMipMessage`` interface to process iMIP data you receive in a client and want to pass on for processing to the backend. 
+
+Please be aware that there are some security considerations to take into account. You can find more infomation on these and the conditions that have to be fulfilled for iMIP data to be processed in the `RFC <https://www.rfc-editor.org/rfc/rfc6047>`_
+
+.. code-block:: php
+
+    <?php
+
+    use OCP\Calendar\IHandleIMipMessage;
+
+    class HandleIMipMessage implements IHandleIMipMessage {
+
+        public function handleIMipMessage(string $name, string $calendarData): void {
+            // Validation and write to your calendar representation
+        }
+
+    }
+
 Resources
 ---------