This is the standard response for successful HTTP requests. The actual response depends on the request method used.

In a GET request, the response contains an entity describing or containing the result of the action.

The request is fulfilled and a new resource is created. The location of the resource is included in the response headers.

The request is processed but no content is returned. The location of the resource is included in the response headers.

The server cannot or will not process the request because something is perceived to be a client error. For example, a malformed request syntax, invalid request message, or a deceptive request routing.

The server cannot process this resource because the current user does not have access to this resource based on the configured scope or a missing privilege. For example, the user is not scoped to the corresponding entity that is being requested.

The requested resource was not found but may be available again in the future. Subsequent requests by the client are allowed.

The request caused a conflict in the system. The response contains a more specific message.

A generic error message. This message is given when an unexpected condition was encountered and no more specific message is suitable.