From f054ffe7607e4a15c52385d60b51dc1ffe74b5e2 Mon Sep 17 00:00:00 2001
From: Erik Johnston <erik@matrix.org>
Date: Tue, 26 Nov 2019 11:40:38 +0000
Subject: [PATCH] Add note about using PUT /state/m.room.member/

---
 proposals/2367-membership-reasons.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/proposals/2367-membership-reasons.md b/proposals/2367-membership-reasons.md
index 479fce34..b43c909c 100644
--- a/proposals/2367-membership-reasons.md
+++ b/proposals/2367-membership-reasons.md
@@ -19,11 +19,15 @@ POST /_matrix/client/r0/rooms/{roomId}/ban
 POST /_matrix/client/r0/rooms/{roomId}/unban
 POST /_matrix/client/r0/rooms/{roomId}/join
 POST /_matrix/client/r0/join/{roomIdOrAlias}
+PUT  /_matrix/client/r0/rooms/{roomId}/state/m.room.member/{userID}
 ```
 
 If specified the `reason` field will be added to the generated membership
 event's content.
 
+*Note: `/state/m.room.member` API currently allows this as clients can specify
+arbitrary content already*
+
 Clients may choose to display the reason for membership events in a room,
 though may not do so if e.g. they have collapsed a set of membership changes.