I Got Tired of Switching Between curl and Postman — So I Built My Own CLI

I didn’t start this project to build “another HTTP tool.” I started it because I was frustrated. Github : https://github.com/I-invincib1e/Httli Every time I worked with APIs, I found myself stuck between two extremes: curl → powerful, but painful to reuse, ugly output, hard to manage workflows Postman → beautiful and powerful, but not scriptable, not terminal-friendly And I kept thinking… Why do I have to choose between these two worlds? The Real Problem The issue wasn’t making a single API request. It was everything around it: Reusing requests Extracting values (like tokens) Running flows (login → fetch → update) Using it inside scripts or CI With curl, I ended up writing messy bash scripts. With Postman, I was clicking around with no automation. There was no clean bridge between the two. The Idea I wanted something simple: A CLI tool that feels like Postman… but behaves like curl. That’s how Httli started. What Httli Became Over time, it turned into something much more than I expecte