From 19a42be01be0a8905762cdbb0f44f589b390e63e Mon Sep 17 00:00:00 2001 From: Olivier 'reivilibre Date: Fri, 22 Sep 2023 17:46:32 +0100 Subject: [PATCH] Note that /logout doesn't take a body --- content/client-server-api/_index.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/content/client-server-api/_index.md b/content/client-server-api/_index.md index 0e7e8473a..b1139cf5d 100644 --- a/content/client-server-api/_index.md +++ b/content/client-server-api/_index.md @@ -23,8 +23,9 @@ Clients are authenticated using opaque `access_token` strings (see [Client Authentication](#client-authentication) for details). All `POST` and `PUT` endpoints, with the exception of [`POST -/_matrix/media/v3/upload`](#post_matrixmediav3upload) and [`PUT -/_matrix/media/v3/upload/{serverName}/{mediaId}`](#put_matrixmediav3uploadservernamemediaid), +/_matrix/media/v3/upload`](#post_matrixmediav3upload), [`PUT +/_matrix/media/v3/upload/{serverName}/{mediaId}`](#put_matrixmediav3uploadservernamemediaid) +and [`POST /_matrix/client/v3/logout`](#post_matrixclientv3logout), require the client to supply a request body containing a (potentially empty) JSON object. Clients should supply a `Content-Type` header of `application/json` for all requests with JSON bodies, but this is not required.