400 BAD request HTTP error code meaning?

rest http error-handling http-status-code-400
Phoenix picture Phoenix · Oct 30, 2013 · Viewed 1.1M times · Source

I have a JSON request which I'm posting to a HTTP URL.

Should this be treated as 400 where requestedResource field exists but "Roman" is an invalid value for this field? 

[{requestedResource:"Roman"}]

Should this be treated as 400 where "blah" field doesn't exist at all?

[{blah:"Roman"}]

Answer

Vidya picture Vidya · Oct 30, 2013

A 400 means that the request was malformed. In other words, the data stream sent by the client to the server didn't follow the rules.

In the case of a REST API with a JSON payload, 400's are typically, and correctly I would say, used to indicate that the JSON is invalid in some way according to the API specification for the service.

By that logic, both the scenarios you provided should be 400s.

Imagine instead this were XML rather than JSON. In both cases, the XML would never pass schema validation--either because of an undefined element or an improper element value. That would be a bad request. Same deal here.

Related questions

REST API error code 500 handling

We are building a new REST API. I was arguing that error code 500 (Internal Server Error) should never be returned. Now, of course if you know the client's params are wrong or something you have everything under control and can …

Read More
Error Handling for Invoke-RestMethod - Powershell

I have a powershell script using the Skytap API (REST). I would like to catch the error, if there is one, and try to display it. For example, we are changing the IP: Invoke-RestMethod -Uri https://cloud.skytap.com/configurations/…

Read More
PUT vs. POST in REST

According to the HTTP/1.1 Spec: The POST method is used to request that the origin server accept the entity enclosed in the request as a new subordinate of the resource identified by the Request-URI in the Request-Line In other words, …

Read More