After trying to figure out why Postman was doing a double GET this morning on a coworker's computer, I finally told him to just install httpie. Took a little while but it's much easier to be explicit about a request. Bash command history does a lot of what these GUIs do.

You probably wanna tell the Postman team[0] about this. They are a bunch of helpful folks who are working very hard on building the product. They'll be glad to see the bug report.

Full disclosure: I interned with Postman for a short duration last year.

[0] - https://twitter.com/postmanclient

Maybe it was actually an OPTION/GET combination? In that case, it's actually useful that Postman is running in Chrome because it shares the same environment and constraints.

Postman can do both. Run in a sandbox or inside Chrome using Postman Interceptor.

You can ping me at @postmanclient or email me at abhinav[at]getpostman.com. Would help in figuring this out.

I find the Collections feature in Postman to be really helpful. Is there a similar feature in Httpie? I couldn't see anything on the github README.

HTTPie is a CLI client, and I don't think it would make sense for it to save the requests you make (as opposed to a GUI). Though, it has a nice persistence feature with sessions (https://github.com/jakubroztocil/httpie#sessions).

It's the nice thing with GUIs (Paw, Postman...)! Paw saves all your work in ".paw" documents that you can share with your team on Dropbox or Git. You can have many documents, and organize your API calls.

Disclaimer: I'm the founder of Paw.

Hello, Paw looks nice.

Can it compare a response to a previously saved response? That would be handy for looking for regressions when refactoring the code behind an API.

Yeah, diffs on JSON responses are something we are thinking about! But tests/assertions are what would make your APIs regression proof.

I didn't know this existed; my curl-fu is weak--this will come in extremely handy. Combined w/ jq this is a new tool in my daily workflow. Thanks!