No we won't. We have a standardized way of dealing with errors in which we will send 400/500 and have an error.data.err and an error.data.message in which err

No we won't. We have a standardized way of dealing with errors in which we will send 400/500 and have an error.data.err and an error.data.message in which err will give a title of the error, and the message elaborating the error in all of our errors across our APIs the reason being is we don't need our developers to memorize dozens of generic status codes, and can be extremely specific in our error.data.err in which status codes can't. It has worked for Facebook, It will work for us.