Been some years since I had to use it (and I think my company jettisoned it shortly thereafter), but at its peak, I remember it doing some things really well that were a PITA to setup locally in a terminal with cURL.

The biggest "Oh my god, this is so much easier" moment was just setting up a tiny JS script onto the login API to stash the bearer token from the return response into a variable, and then propagate it into the header of all subsequent calls. Trying to script THAT in Bash (parsing the bearer token from the return response) was also a headache and never worked 100% for me.

Although that was me trying to do it manually. I'm sure a vibe-coded solution would probably work well enough these days.

I think because editing in terminals text was not a good development experience, navigating the curdor, and pressing Enter would issue the command.

Personally I use a wrapper cli I built myself over curl which automatically gets api docs of my product and easily get the token so its great for agents

I was on a team where work was often presented and demo'd to semi technical managers and stakeholders. For the backend guys, this was the best we had.

Nice to see the leaner alternatives people are suggesting here.

Makes it easy to not so technical testers to .. test the API. Share the collection, just point at their own test server and off they go. No command line knowhow needed.

nah, a python script that wraps what needs wrapping has been my go-to since that day Postman said I had to log in