Interesting, seems like the upcoming &quot;Hello World&quot; for API services :-)<p>I also made a &quot;return the HTTP code you request&quot;-service like this, but with another design choice than in this one and some others like <a href="http:&#x2F;&#x2F;httpbin.org&#x2F;" rel="nofollow">http:&#x2F;&#x2F;httpbin.org&#x2F;</a>, <a href="https:&#x2F;&#x2F;httpstatuses.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;httpstatuses.com&#x2F;</a>, <a href="http:&#x2F;&#x2F;httpstat.us&#x2F;" rel="nofollow">http:&#x2F;&#x2F;httpstat.us&#x2F;</a>.<p>Instead of specifying the requested HTTP code in the URL path, I put the requested HTTP code in the URL query, basically ignoring the URL path. In that way, the URL path -- the resource identification in a REST-styled API -- can stay whatever you want as you&#x27;re specifying the requested status code as query parameter. This made testing a program that uses resources in a REST API easier, as I don&#x27;t need to rewrite the URL path, but just require to add a query parameter in my test code.<p>Example: instead of <a href="http:&#x2F;&#x2F;example.com&#x2F;404" rel="nofollow">http:&#x2F;&#x2F;example.com&#x2F;404</a> I request  <a href="http:&#x2F;&#x2F;example.com&#x2F;resource&#x2F;id?response=404" rel="nofollow">http:&#x2F;&#x2F;example.com&#x2F;resource&#x2F;id?response=404</a> to get a 404 response. <a href="http:&#x2F;&#x2F;example.com&#x2F;resource&#x2F;another-id?response=200" rel="nofollow">http:&#x2F;&#x2F;example.com&#x2F;resource&#x2F;another-id?response=200</a> gets a 200 code.