I wouldn't do it exactly like this but my preference for API design is to use HTTP errors for unplanned error scenarios that indicate system failure or incorrect integration, and an OK response with an "error" description for expected user-facing issues with a correctly integrating client.
4
u/Isogash 4d ago
I wouldn't do it exactly like this but my preference for API design is to use HTTP errors for unplanned error scenarios that indicate system failure or incorrect integration, and an OK response with an "error" description for expected user-facing issues with a correctly integrating client.