The request succeeded. The result meaning of "success" depends on the HTTP method:

The request succeeded, and a new resource was created as a result. This is typically the response sent after POST requests, or some PUT requests.

The request has been received but not yet acted upon. It is noncommittal, since there is no way in HTTP to later send an asynchronous response indicating the outcome of the request. It is intended for cases where another process or server handles the request, or for batch processing.

This response code means the returned metadata is not exactly the same as is available from the origin server, but is collected from a local or a third-party copy. This is mostly used for mirrors or backups of another resource. Except for that specific case, the 200 OK response is preferred to this status.

There is no content to send for this request, but the headers may be useful. The user agent may update its cached headers for this resource with the new ones.

Tells the user agent to reset the document which sent this request.

This response code is used when the Range header is sent from the client to request only part of a resource.

Conveys information about multiple resources, for situations where multiple status codes might be appropriate.

Used inside a response element to avoid repeatedly enumerating the internal members of multiple bindings to the same collection.

The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.