Status
Types
The request cannot be processed without authentication. WWW-Authenticate header must be populated with an authentication challenge.
The request has failed due to a client error.
The request has failed.
The user lacks the needed permissions to access the method.
The server reached an unexpected condition during processing.
The request is invalid and was not processed.
The server does not implement the requested method.
The server is under heavy load and can't complete the request.
The request has succeeded.
The payload of the request is larger than the server is willing to process. Payload size-limits are decided by each server.
The client has sent too many requests. Rate-limits are decided by each server. Retry-After header may be populated with the amount of time that must pass before the next request.
The request has failed due to a server error.
The execution of the procedure depends on a call to another server which has failed.
The execution of the procedure depends on a call to another server which timed out.
The interpretation of a 404 response is somewhat unique for XRPC. A 404 indicates that the server does not provide a resource at the given location (/xrpc) meaning the server does not support XRPC. To indicate that the given procedure is not implemented, use MethodNotImplemented.