Profile endpoint still accepts "field" parameter

matrix-org · Jun 9, 2024 · a750e53 · a750e53
1 parent 0b88d85
commit a750e53
Showing 1 changed file with 3 additions and 1 deletion.
diff --git a/proposals/4133-extended-profiles.md b/proposals/4133-extended-profiles.md
@@ -68,7 +68,9 @@ member events.
 3. **DELETE `/_matrix/client/v3/profile/{userId}/{key_name}`**: This endpoint will remove the key
    (and associated value) from the profile, if permitted by the homeserver.
 
-4. **GET `/_matrix/client/v3/profile/{userId}/`**: This endpoint will retrieve all profile fields:
+4. **GET `/_matrix/client/v3/profile/{userId}/`**: This endpoint will retrieve all profile fields,
+   and as per the current stable endpoint, accepts an optional `field` query string parameter to
+   request a single field:
 
     ```json
     {