Companion
Properties
Request contained valid JSON, but it was malformed in some way, e.g. missing required keys, invalid values for keys.
(Not documented yet).
The state change requested cannot be performed, such as attempting to unban a user who is not banned.
The user is unable to reject an invite to join the server notices room. See the Server Notices module for more information.
The Captcha provided did not match what was expected.
A Captcha is required to complete the request.
(Not documented yet).
The resource being requested is reserved by an application service, or the application service making the request has not created the resource.
Forbidden access, e.g. joining a room without permission, failed login.
The room or resource does not permit guests to access it.
The client attempted to join a room that has a version the server does not support. Inspect the room_version property of the error response for the room's version.
A parameter that was specified has the wrong value. For example, the server expected an integer and instead received a string.
Sent when the initial state given to the createRoom API is invalid.
Encountered when trying to register a user ID which is not valid.
Too many requests have been sent in a short period of time. Wait a while then try again.
(Not documented yet).
A required parameter was missing from the request.
No access token was specified for the request.
No resource was found for this request.
Request did not contain valid JSON.
(Not documented yet).
The password was found in a dictionary, and is not acceptable.
The password doesn't contain any digit but the server requires at least one.
The password doesn't contain any lowercase letter but the server requires at least one.
The password doesn't contain any symbol but the server requires at least one.
The password doesn't contain any uppercase letter but the server requires at least one.
The provided password's length is shorter than the minimum length required by the server.
The request cannot be completed because the homeserver has reached a resource limit imposed on it. For example, a homeserver held in a shared hosting environment may reach a resource limit if it starts using too much memory or disk space. The error MUST have an admin_contact field to provide the user receiving the error a place to reach out to. Typically, this error will appear on routes which attempt to modify state (eg: sending messages, account data, etc) and not routes which only read state (eg: /sync, get account data, etc).
Sent when the room alias given to the createRoom API is already in use.
The client's request used a third party server, eg. identity server, that this server does not trust.
Authentication could not be performed on the third party identifier.
The server does not permit this third party identifier. This may happen if the server only permits, for example, email addresses from a particular domain.
Sent when a threepid given to an API cannot be used because the same threepid is already in use.
Sent when a threepid given to an API cannot be used because no record matching the threepid was found.
The request or entity was too large.
The request was not correctly authorized. Usually due to login failures.
The access token specified was not recognised.
The server did not understand the request.
The client's request to create a room used a room version that the server does not support.
The user ID associated with the request has been deactivated. Typically for endpoints that prove authentication, such as /login.
Encountered when trying to register a user ID which has been taken.
(Not documented yet).
(Not documented yet).
The user account has expired. It has to be renewed by clicking on an email or by sending a renewal token.