Clarify string formats in user data endpoints

Signed-off-by: Kévin Commaille <zecakeh@tedomum.fr>
This commit is contained in:
Kévin Commaille 2026-04-22 12:19:15 +02:00
parent c68e687a8c
commit 7c3e5148ac
No known key found for this signature in database
GPG key ID: F26F4BE20A08255B
2 changed files with 16 additions and 6 deletions

View file

@ -46,6 +46,8 @@ paths:
example: "@alice:example.com"
schema:
type: string
format: mx-user-id
pattern: "^@"
- in: path
name: keyName
description: The name of the profile field to set. This MUST be either
@ -158,6 +160,8 @@ paths:
example: "@alice:example.com"
schema:
type: string
format: mx-user-id
pattern: "^@"
- in: path
name: keyName
description: The name of the profile field to retrieve.
@ -216,6 +220,8 @@ paths:
example: "@alice:example.com"
schema:
type: string
format: mx-user-id
pattern: "^@"
- in: path
name: keyName
description: The name of the profile field to delete.
@ -286,6 +292,8 @@ paths:
example: "@alice:example.com"
schema:
type: string
format: mx-user-id
pattern: "^@"
responses:
"200":
description: The profile information for this user.

View file

@ -82,6 +82,8 @@ paths:
type: string
example: "@foo:bar.com"
description: The user's matrix user ID.
format: mx-user-id
pattern: "^@"
display_name:
type: string
example: Foo