EDIT: sorry, I was cranky. I just really don't like Postman/its UI/BS. To each his/her own.

Weird take. Just because you can use curl it doesn’t mean you can’t value a GUI to be able to store and manipulate requests quickly and view a formatted response body.

I use postman all the time to explore apis. Sure I could do it from the command line, but this is quicker and it saves my request payloads.

(Though now I’m obviously open to suggestions for better tools)

▲

tempestrose an hour ago | parent | next [-]

Get an older copy of fiddler.

▲

thisIsFiner 35 minutes ago | parent | prev | next [-]

Weird take. I thought for myself about the problem and solved it rather than externalize such and end up locked into an increasingly abusive relationship.

Been using homegrown scripts designed around wget and curl, accessible as shell aliases so I save time never downloading Postman or developing muscle memory for it, yet can still explore APIs

There's an idea for a better tool; the one you patch right in to your workflow to avoid context switches to a GUI mental model; I just focus on computer generating data rather than color of the virtual captains chair

	▲	bfbf 11 minutes ago \| parent [-]
		Not sure if you’re trolling but writing “homegrown scripts as shell aliases” is not faster than a gui. I totally agree Postman is enshittified, but when I just want to see a sample response for given input data, it does the job. Sure I’d like a more lightweight tool, but there’s no way I’m “context switching” to writing shell scripts when I just want to check a single endpoint. (I’d also wager than in many cases, opening a gui and hitting send on a pre-saved request is faster than using an llm too) You can do what you like though, my original comment was against the gatekeeping and punching down. I don’t care one way or another what tool you use, but let’s not make people inferior because they aren’t using a TUI for everything.

▲

syhol an hour ago | parent | prev [-]

[dead]