What HTTP code should my API use if the resource does not exist

Question

In a REST API which HTTP code should I use if the client calls a non existing resource?

Ex:

GET /messsssssssages/42

I already map every other http codes (resource not found = 404 etc...) but I can't decide how to map this one.

I hesitate between 404 and 400. For my comprehension, in REST API 404 is for a resource not found (the id is not present in DB) here, this is clearly a routing error. Should it be a 404? I don't know... — nemenems
– nemenems, Commented Dec 14, 2016 at 10:28

cosbor11 · Accepted Answer · 2016-12-14 10:27:51Z

2

404 Not Found

The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused.

You can map 404 Not found to a valid resource that does not have an instance with that ID and can also map 404 to there is no resource by that name.

answered Dec 14, 2016 at 10:27

cosbor11

16.4k11 gold badges62 silver badges76 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

What HTTP code should my API use if the resource does not exist

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related