From 59cfacf94fe87b15e190c19f29dec272c22fcaf4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?K=C3=A9vin=20Commaille?= Date: Wed, 17 Dec 2025 10:39:06 +0100 Subject: [PATCH] Remove duplicate endpoint behavior MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Kévin Commaille --- content/application-service-api.md | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/content/application-service-api.md b/content/application-service-api.md index 42b1b985..5f6b17ab 100644 --- a/content/application-service-api.md +++ b/content/application-service-api.md @@ -547,19 +547,13 @@ client-server endpoint. Application services need to be able to create and delete devices to manage the encryption for their users without having to rely on `/login`, which also generates an access token for the user, and which might not be available for -homeservers that only support the [OAuth 2.0 API](client-server-api/#oauth-20-api). +homeservers that only support the [OAuth 2.0 API](/client-server-api/#oauth-20-api). ##### Creating devices Application services can use the [`PUT /_matrix/client/v3/devices/{deviceId}`](/client-server-api/#put_matrixclientv3devicesdeviceid) endpoint to create new devices. -When a new device was created, the homeserver MUST return a 201 HTTP status code. -It MUST still return a 200 HTTP status code if a device was updated. - -This endpoint is rate-limited for device creation. Servers MAY want to use login -rate limits. - ##### Deleting devices The following endpoints used to delete devices MUST NOT require [User-Interactive