The "HTTP" format proposed in the article is the same we use with Hurl [1], an Open Source HTTP CLI based on plain text. POST http://httpbingo.org/anything/c

The "HTTP" format proposed in the article is the same we use with Hurl [1], an Open Source HTTP CLI based on plain text. POST http://httpbingo.org/anything/chat content-type: application/json { "message": "Hello!" } We extend it a bit to add checks on response, and add request chaining, but it's basically HTTP 1.x as this article shows it. A lot of others tools have the same idea, with minor differences: - Hurl (I'm one of the maintainer) https://hurl.dev https://hurl.dev - HTTP Client https://www.jetbrains.com/help/idea/http-client-in-product-code-editor.html https://www.jetbrains.com/help/idea/http-client-in-product-c... - httpYac https://httpyac.github.io https://httpyac.github.io - restclient.el https://github.com/pashky/restclient.el https://github.com/pashky/restclient.el - REST Client https://github.com/Huachao/vscode-restclient https://github.com/Huachao/vscode-restclient - verb https://github.com/federicotdn/verb https://github.com/federicotdn/verb And many more... Worth noting, other tools have taken the YAML route (like Step CI https://stepci.com https://stepci.com), JavaScript (k6 https://k6.io/docs/using-k6/http-requests/ https://k6.io/docs/using-k6/http-requests/)... I'm biased of course, I've a tiny preference for the simple plain text format. And of course, there are also GUI application (Postman, Insomnia, RecipeUI amon others) [1]: https://hurl.dev https://hurl.dev