From 8cb0b3e7f6e0cd0844c1fba93a0555b7a5f5d64f Mon Sep 17 00:00:00 2001 From: Hugh Nimmo-Smith Date: Thu, 25 Sep 2025 09:04:41 +0100 Subject: [PATCH] Update data/api/client-server/profile.yaml Co-authored-by: Johannes Marbach --- data/api/client-server/profile.yaml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/data/api/client-server/profile.yaml b/data/api/client-server/profile.yaml index c426059f..6814ccb5 100644 --- a/data/api/client-server/profile.yaml +++ b/data/api/client-server/profile.yaml @@ -31,9 +31,9 @@ paths: field, including its key and value, SHOULD use the `DELETE` endpoint instead. This endpoint uses [capabilities negotiation](/client-server-api/#capabilities-negotiation) - depending on the `keyName`. - For the `displayname` key, clients SHOULD check the value of the [`m.set_displayname` capability](/client-server-api/#mset_displayname-capability). - For the `avatar_url` key, clients SHOULD check the value of the [`m.set_avatar_url` capability](/client-server-api/#mset_avatar_url-capability). + depending on the `keyName`. Clients SHOULD check the value of the + [`m.profile_fields` capability](/client-server-api/#mprofile_fields-capability) to detect + which `keyName`s they are allowed to modify. operationId: setProfileField security: - accessTokenQuery: []