|
|
|
|
|
|
by vfaronov
3231 days ago
|
|
|
> In most cases it is clearer to simply adopt a payload format that includes application specific error codes Absolutely. This is a common practice and there’s even a proposed standard for it (RFC 7807). But such a payload need not be sent with 200 (OK). It can refine the status code instead of overriding it. |
|
|
True, this is sometimes possible when (coincidentally) one of the HTTP specs or extensions defines one of the codes in a way that feels similar enough.
The mistake is to assume that there is already a code for everything and that one does not need to define application specific error codes, which is what many API developers do.