Who’s bad? The original release of badapi.net was a bit limited – you could get whatever error response you needed, but only if you changed your client to point to the badapi.net URLs – so if you want to test that your client behaves differently when it gets a 500 from the server, you had to change the code to point to http://badapi.net/internals... With the new release (from commit 6ab647e), badapi.net now has dedicated host names for the common error responses, and they can take any URL. ......
I've had a need in a few projects for a REST API that doesn't behave well - takes a long time to respond, or never responds, returns unexpected status codes etc.That can be very useful for testing that clients cope gracefully with unexpected responses.Till now I've always coded a stub API in the project and run it locally, but I've put a few 'misbehaved' endpoints together and published them at www.badapi.net, and the source is on GitHub here: sixeyed/badapi.net.You can browse to the home page and ......