From 4297109c1198ba7a5d50a8072d07fd49465c810b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?K=C3=A9vin=20Commaille?= Date: Thu, 15 Jan 2026 11:19:31 +0100 Subject: [PATCH] Apply sugggestions to RequestTokenResponse MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Kévin Commaille --- .../client-server/definitions/request_token_response.yaml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/data/api/client-server/definitions/request_token_response.yaml b/data/api/client-server/definitions/request_token_response.yaml index 2f4216aa..67afc6ab 100644 --- a/data/api/client-server/definitions/request_token_response.yaml +++ b/data/api/client-server/definitions/request_token_response.yaml @@ -33,13 +33,14 @@ properties: validation token, with identical request and response parameters and error codes to the Identity Service API's [`POST /_matrix/identity/v2/validate/email/submitToken`](/identity-service-api/#post_matrixidentityv2validateemailsubmittoken) - endpoint (without the requirement for an access token). The homeserver + and [`POST /_matrix/identity/v2/validate/msisdn/submitToken`](/identity-service-api/#post_matrixidentityv2validatemsisdnsubmittoken) + endpoints (without the requirement for an access token). The homeserver must send this token to the user (if applicable), who should then be prompted to provide it to the client. If this field is not present, the client can assume that verification will happen without the client's involvement provided the homeserver - advertises this specification version in the [`GET /versions`](/client-server-api/#get_matrixclientversions) + advertises a sufficiently recent version in the [`GET /versions`](/client-server-api/#get_matrixclientversions) response (ie: r0.5.0). example: "https://example.org/path/to/submitToken" required: ['sid']