{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://www.devtools.tools"},{"@type":"ListItem","position":2,"name":"HTTP Status Codes","item":"https://www.devtools.tools/http-status"},{"@type":"ListItem","position":3,"name":"200 OK","item":"https://www.devtools.tools/http-status/200"}]}All HTTP status codes
HTTP 200 OK
SuccessThe request succeeded. The response body contains the result — a page for GET, the operation outcome for POST.
Defined in RFC 9110
Common causes
- Normal successful request
How to fix it
Nothing to fix
If you expected different content with a 200, check caching layers and the application logic, not the transport
Related status codes
201 Created
The request succeeded and a new resource was created. The Location header usually points at the new resource — the canonical response for a successful POST in REST APIs.
204 No ContentThe request succeeded and there is intentionally no response body. Typical for DELETE operations and for PUT/PATCH when the server returns nothing.
Want to explore status codes interactively? Try the free HTTP Status Code Reference — search, categories and example responses, right in your browser.