200 OK

All status codes
2xx · Successterminal

200OK

The request has succeeded. The information returned via the response depends on the method used in the request.

What this code obliges you to do

Retry

Do not retry automatically

Repeating the same request produces the same result. A retry loop here just multiplies load and hides the real fault.

Caching

Cacheable by default

RFC 9110 lists this code as heuristically cacheable, so a cache may store it even with no Cache-Control header. Send explicit headers if that is not what you want.

Response body

Body allowed

You may return a payload explaining the outcome — for an error, a machine-readable problem document is worth the effort.

When you see it

2
1

Successful page load

2

Successful API data retrieval

Effect on search

Ideal status for SEO. Search engines will aggressively index pages returning 200 OK.

How to send it

2
Node.js (Express)
res.status(200).send({ message: 'Success' });
Python (FastAPI)
return {'message': 'Success'}

Codes people confuse with this one

2
Class2xx
RetryNo
CacheDefault
BodyAllowed