Standard response for successful HTTP requests. The actual response depends on the request method used.

In a GET request, the response contains an entity corresponding to the requested resource.

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

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

The request has been processed, but no content is returned. The response is typical with PUT and DELETE requests.

The server cannot or will not process the request because something is perceived to be a client error, such as malformed request syntax, invalid request message framing, or 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 missing privilege. For example, the user is not scoped to the corresponding entity that is being requested.

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

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

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