When submitting over the API, I would like to tell the difference between an invalid request (malformed, failed authentication, non-existent task etc.) and a valid, but rejected request (too many submissions, wrong file names etc.).
Currently, the API uses status code 400 for rejected submissions and as far as I know other status codes in the other situations. However, I am not happy with matching a very broad status code in my client.
I suggest that we use status 422 (Unprocessable Content, defined as "well formed, but could not be processed") for rejected submissions.
When submitting over the API, I would like to tell the difference between an invalid request (malformed, failed authentication, non-existent task etc.) and a valid, but rejected request (too many submissions, wrong file names etc.).
Currently, the API uses status code 400 for rejected submissions and as far as I know other status codes in the other situations. However, I am not happy with matching a very broad status code in my client.
I suggest that we use status 422 (Unprocessable Content, defined as "well formed, but could not be processed") for rejected submissions.