@@ -87,39 +87,6 @@ method SHOULD NOT delete the key but rather retain it with a `null` value. Serve
87
87
}
88
88
```
89
89
90
- ### Partially Update Profile Fields
91
-
92
- - ** Endpoint** : ` PATCH /_matrix/client/v3/profile/{userId} `
93
- - ** Description** : Merge the provided JSON object into the user's profile, updating any
94
- specified keys without altering others, if permitted by the homeserver.
95
- - ** Request Body** :
96
-
97
- ``` json
98
- {
99
- "avatar_url" : " mxc://matrix.org/MyNewAvatar" ,
100
- "displayname" : " John Doe" ,
101
- "m.example_field" : " new_value1"
102
- }
103
- ```
104
-
105
- ### Replace Profile Fields
106
-
107
- - ** Endpoint** : ` PUT /_matrix/client/v3/profile/{userId} `
108
- - ** Description** : Replace the entire user's profile with the provided JSON object,
109
- adding or updating keys and removing any absent ones, if permitted by the homeserver.
110
- - ** Request Body** :
111
-
112
- ``` json
113
- {
114
- "avatar_url" : " mxc://matrix.org/MyNewAvatar" ,
115
- "displayname" : " John Doe" ,
116
- "m.example_field" : " new_value1"
117
- }
118
- ```
119
-
120
- ** Note** : Clients are encouraged to manipulate fields individually to avoid race conditions.
121
- However, this method allows for bulk updates when needed (e.g. bots managing multiple accounts).
122
-
123
90
## Server-Server API Changes
124
91
125
92
The federation endpoint ` GET /_matrix/federation/v1/query/profile ` will mirror the client-server
@@ -239,12 +206,12 @@ demonstrates the process of defining new fields in the `m.*` namespace.
239
206
240
207
### 403 Forbidden: User Lacks Permission
241
208
242
- ** Note** : See [ MSC4170] ( https://github.com/matrix-org/matrix-spec-proposals/pull/4170 ) for more
243
- discussion on how server policy may result in 403 errors for profile requests.
209
+ Unchanged from the [ current spec] ( https://spec.matrix.org/v1.13/client-server-api/#server-behaviour ) .
244
210
245
211
### 404 Not Found: Target Cannot Be Found
246
212
247
- - ** ` M_NOT_FOUND ` ** : Profile key does not exist.
213
+ - ** ` M_NOT_FOUND ` ** : Profile key does not exist (this is unchanged, just expanded to
214
+ apply to arbitrary keys).
248
215
249
216
``` json
250
217
{
@@ -378,9 +345,6 @@ Use unstable endpoints when the capability is not yet stable:
378
345
- ** Get/Set/Delete Profile Fields** :
379
346
- ` /_matrix/client/unstable/uk.tcpip.msc4133/profile/{userId}/{key_name} `
380
347
381
- - ** Patch/Put Profile** :
382
- - ` /_matrix/client/unstable/uk.tcpip.msc4133/profile/{userId} `
383
-
384
348
### Unstable Capability
385
349
386
350
Advertise the capability with an unstable prefix:
0 commit comments