From 2783820f98b02f01dd2d55aca1e05fc3e78a617d Mon Sep 17 00:00:00 2001
From: Will Hunt <will@half-shot.uk>
Date: Thu, 3 May 2018 12:23:24 +0100
Subject: [PATCH] Initial draft of GET media/limits

---
 api/client-server/content-repo.yaml | 27 +++++++++++++++++++++++++++
 1 file changed, 27 insertions(+)

diff --git a/api/client-server/content-repo.yaml b/api/client-server/content-repo.yaml
index 03a25fd9..6e3ba273 100644
--- a/api/client-server/content-repo.yaml
+++ b/api/client-server/content-repo.yaml
@@ -269,3 +269,30 @@ paths:
             "$ref": "definitions/error.yaml"
       tags:
         - Media
+  "/limits":
+    get:
+      summary: Get limits on what can be uploaded to the content repository.
+               Clients SHOULD use this as a guide when uploading content.
+               All values are intentionally left optional, the client MUST assume
+               that any field not given is not limited.
+
+               **NOTE:** Reverse proxies may apply their own limits.
+      operationId: getLimits
+      produces: ["application/json"]
+      security:
+        - accessToken: []
+      responses:
+        200:
+          description: The limits exposed by the matrix server.
+          schema:
+            type: object
+            properties:
+              size:
+                type: number
+                description: "The maximum size a upload can be in bytes."
+          examples:
+            application/json: {
+                "size": 50000000
+              }
+      tags:
+        - Media