Remove duplicate endpoint behavior

Signed-off-by: Kévin Commaille <zecakeh@tedomum.fr>
This commit is contained in:
Kévin Commaille 2025-12-17 10:39:06 +01:00
parent c71c1e225b
commit 59cfacf94f
No known key found for this signature in database
GPG key ID: F26F4BE20A08255B

View file

@ -547,19 +547,13 @@ client-server endpoint.
Application services need to be able to create and delete devices to manage the 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 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 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 ##### Creating devices
Application services can use the [`PUT /_matrix/client/v3/devices/{deviceId}`](/client-server-api/#put_matrixclientv3devicesdeviceid) Application services can use the [`PUT /_matrix/client/v3/devices/{deviceId}`](/client-server-api/#put_matrixclientv3devicesdeviceid)
endpoint to create new devices. 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 ##### Deleting devices
The following endpoints used to delete devices MUST NOT require [User-Interactive The following endpoints used to delete devices MUST NOT require [User-Interactive