200 OK
The request succeeded. What the body contains depends on the method: the resource for GET, the result of the action for POST.
2xx · Success
Typical causes
The normal outcome. A 200 with an error message in the body is an API design mistake: clients and monitors will read it as success.
On Bex
The activator answers GET /healthz on a hibernating app with 200 before it looks up the app, so a probe on that path alone can report healthy while real routes still get the wake 503. Probe an application-owned readiness URL instead.
Defined in RFC 9110, §15.3.1