Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2026-04-07 20:04:09 +02:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Format as definition

Browse source
This commit is contained in:
Hugh Nimmo-Smith 2026-03-04 10:22:49 +00:00
parent 0445ab222e
commit 07cef68485
1 changed files with 13 additions and 13 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

26
content/client-server-api/_index.md
View file

@ -148,35 +148,35 @@ only read state (e.g.: [`/sync`](#get_matrixclientv3sync),
[`/user/{userId}/account_data/{type}`](#get_matrixclientv3useruseridaccount_datatype), etc). [`/user/{userId}/account_data/{type}`](#get_matrixclientv3useruseridaccount_datatype), etc).
`M_USER_LIMIT_EXCEEDED` `M_USER_LIMIT_EXCEEDED`
{{% added-in v="1.18" %}} The request cannot be completed because the user has : {{% added-in v="1.18" %}} The request cannot be completed because the user has
exceeded (or the request would cause them to exceed) a limit associated with exceeded (or the request would cause them to exceed) a limit associated with
their account. For example, a user may have reached their allocated storage their account. For example, a user may have reached their allocated storage
quota, reached a maximum number of allowed rooms, devices, or other quota, reached a maximum number of allowed rooms, devices, or other
account-scoped resources, or exceeded usage limits for specific features. account-scoped resources, or exceeded usage limits for specific features.
The error response MUST have an `info_uri` field (string), which is a URI : The error response MUST have an `info_uri` field (string), which is a URI
that the client can present to the user to provide more context on the that the client can present to the user to provide more context on the
encountered limit and, if applicable, guidance on how to increase the limit. encountered limit and, if applicable, guidance on how to increase the limit.
The homeserver MAY return different values for `info_uri` depending on the type The homeserver MAY return different values for `info_uri` depending on the type
of limit reached. of limit reached.
The error response MAY include a `can_upgrade` field (boolean, default `false`). : The error response MAY include a `can_upgrade` field (boolean, default `false`).
If `true`, it indicates that the specific limit encountered can be increased, If `true`, it indicates that the specific limit encountered can be increased,
for example by upgrading the user's account tier. If absent or `false`, the for example by upgrading the user's account tier. If absent or `false`, the
limit is a hard limit that cannot be increased. limit is a hard limit that cannot be increased.
The HTTP status code will depend on depend on the particular endpoint. : The HTTP status code will depend on depend on the particular endpoint.
Example response: : Example response:
```json ```json
{ {
"errcode": "M_USER_LIMIT_EXCEEDED", "errcode": "M_USER_LIMIT_EXCEEDED",
"error": "You have exceeded your storage quota of 10GB", "error": "You have exceeded your storage quota of 10GB",
"info_uri": "https://example.com/homeserver/about?limit_type=quota", "info_uri": "https://example.com/homeserver/about?limit_type=quota",
"can_upgrade": true "can_upgrade": true
} }
``` ```
`M_UNKNOWN` `M_UNKNOWN`
: An unknown error has occurred. : An unknown error has occurred.