Oliver Nassar

HTTP Status Code API Endpoints

February 2024

Another simple one: 63 API endpoints that will return the exact HTTP Status Code (and Status Message) you're looking for.

The API structure is simple:

https://aws-api.416.io/sc/v1/{statusCode}


That's it! Swap in the desired HTTP Status Code you're looking to test, and you'll get that response back (along with metadata associated with that status code).

Below are a list of all the status codes supported:

https://aws-api.416.io/sc/v1/100
https://aws-api.416.io/sc/v1/101
https://aws-api.416.io/sc/v1/102
https://aws-api.416.io/sc/v1/103
https://aws-api.416.io/sc/v1/200
https://aws-api.416.io/sc/v1/201
https://aws-api.416.io/sc/v1/202
https://aws-api.416.io/sc/v1/203
https://aws-api.416.io/sc/v1/204
https://aws-api.416.io/sc/v1/205
https://aws-api.416.io/sc/v1/206
https://aws-api.416.io/sc/v1/207
https://aws-api.416.io/sc/v1/208
https://aws-api.416.io/sc/v1/226
https://aws-api.416.io/sc/v1/300
https://aws-api.416.io/sc/v1/301
https://aws-api.416.io/sc/v1/302
https://aws-api.416.io/sc/v1/303
https://aws-api.416.io/sc/v1/304
https://aws-api.416.io/sc/v1/305
https://aws-api.416.io/sc/v1/306
https://aws-api.416.io/sc/v1/307
https://aws-api.416.io/sc/v1/308
https://aws-api.416.io/sc/v1/400
https://aws-api.416.io/sc/v1/401
https://aws-api.416.io/sc/v1/402
https://aws-api.416.io/sc/v1/403
https://aws-api.416.io/sc/v1/404
https://aws-api.416.io/sc/v1/405
https://aws-api.416.io/sc/v1/406
https://aws-api.416.io/sc/v1/407
https://aws-api.416.io/sc/v1/408
https://aws-api.416.io/sc/v1/409
https://aws-api.416.io/sc/v1/410
https://aws-api.416.io/sc/v1/411
https://aws-api.416.io/sc/v1/412
https://aws-api.416.io/sc/v1/413
https://aws-api.416.io/sc/v1/414
https://aws-api.416.io/sc/v1/415
https://aws-api.416.io/sc/v1/416
https://aws-api.416.io/sc/v1/417
https://aws-api.416.io/sc/v1/418
https://aws-api.416.io/sc/v1/421
https://aws-api.416.io/sc/v1/422
https://aws-api.416.io/sc/v1/423
https://aws-api.416.io/sc/v1/424
https://aws-api.416.io/sc/v1/426
https://aws-api.416.io/sc/v1/428
https://aws-api.416.io/sc/v1/429
https://aws-api.416.io/sc/v1/431
https://aws-api.416.io/sc/v1/451
https://aws-api.416.io/sc/v1/500
https://aws-api.416.io/sc/v1/501
https://aws-api.416.io/sc/v1/502
https://aws-api.416.io/sc/v1/503
https://aws-api.416.io/sc/v1/504
https://aws-api.416.io/sc/v1/505
https://aws-api.416.io/sc/v1/506
https://aws-api.416.io/sc/v1/507
https://aws-api.416.io/sc/v1/508
https://aws-api.416.io/sc/v1/509
https://aws-api.416.io/sc/v1/510
https://aws-api.416.io/sc/v1/511


Why did I build this?

While building the webhooks system for Zenlogin I found I was creating fake endpoints to mimic failed requests. This was a simple tool (that would always be up via AWS Lambda and API Gateway).


How was it built?

Only two AWS services needed for this one:


Feedback

This should work perfectly fine for testing. If you plan on using this at scale (e.g. in a cron that hits the endpoint every few minutes), let me know and I can set up something more scalable: onassar@gmail.com