What 200 OK means
200 OK indicates that the request succeeded. For GET and HEAD, the body contains the requested representation. For PUT and PATCH, it usually contains the updated resource. For POST, it means the action succeeded but did not create a new resource with its own URL — that case is 201.
When a server should return it
- A GET request returned the requested resource.
- A PUT or PATCH updated a resource and the response includes the new state.
- A POST performed an action without creating a new addressable resource.
- A DELETE succeeded and the server wants to return a confirmation body (204 is more common).
Example response
HTTP/1.1 200 OK
Content-Type: application/json
Cache-Control: no-store
{"id": 42, "name": "Ada"}Why you might see it unexpectedly
- A proxy or cache returning a stale success payload.
- An API returning 200 with an error object in the body — a contract issue, not a protocol one.
- A request that should have been 201 or 204 but used a generic success path.
Related status codes
201 Created is the correct code when a POST creates a new resource. 204 No Content is preferable when there is nothing to return. 304 Not Modified is a special success case for conditional requests.