From af3d0fcb8dbbd9e2faf179f6e157a00d1c797d41 Mon Sep 17 00:00:00 2001 From: Nick Mills-Barrett Date: Sat, 10 Aug 2024 13:53:24 +0100 Subject: [PATCH] Use correct API versions --- proposals/3870-media-async-upload-url.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/proposals/3870-media-async-upload-url.md b/proposals/3870-media-async-upload-url.md index 9caab840c..4ff45a33f 100644 --- a/proposals/3870-media-async-upload-url.md +++ b/proposals/3870-media-async-upload-url.md @@ -23,7 +23,7 @@ The proposal modifies the MSC2246 create endpoint to optionally include a URL th client may use to upload the content for the created MXID. This is considered optional and the client may continue to upload via the new upload endpoint defined in MSC2246. -`POST /_matrix/media/v3/create` +`POST /_matrix/media/v1/create` **Example response** @@ -44,7 +44,7 @@ The response to the upload is implementation specific depending on the target se should interpret standard HTTP responses, a 200 or 201 indicating successful upload. Once the upload is complete, the client must notify the media server via a new endpoint: -`POST /_matrix/media/v3/upload/{serverName}/{mediaId}/complete` +`POST /_matrix/media/v1/upload/{serverName}/{mediaId}/complete` **Example response**