I've been using curl, like forever. I don't understand the preoccupation for using postman, et. al. -- why pay for something that literally requires a little bit of light RTFM?
People absolutely will pay for software rather than reading or thinking, if it makes doing the work easier. You may have heard of this thing called chatgpt.
(not being a web developer, I've only lightly used Postman, and it is definitely handy for things like authentication. Especially once you touch OAuth. But I uninstalled it once they went unnecessarily cloud)
Not sure how some developers could be so allergic to the terminal, don't you already spend a lot of time there?
Who says I'm allergic to the terminal? I already stated that I use curl.
I could also ask why are some developers so allergic to any kind of UI. And they're very vocal about it. Just use whatever you want.
Preferring "a couple of clicks" vs "run one command" seems to indicate so, otherwise I'm not sure why'd someone would prefer the former instead of the latter.
Actually I don't even create those collections, we have OpenAPI/Swagger docs for all of our APIs and I just import them with a couple of clicks (which I'm sure there's a way to do with curl).
For the odd requests, and sharing requests with others? I use curl, no problem. I actually think I know it pretty well and very rarely need to look up any docs for it.
No, I don't (what a shitty strawman), I create abstractions then, like any other project. Surely you don't have hundreds of completely original and bespoke requests? Previously I've handled thousands of requests by having a .csv to load from.
Absolutely I do. It’s not like a few hundred endpoints is out of the ordinary in any mid sized company.
I can go an edit any of the requests with autoformatting, highlighting and whatnot.
As I say, you can keep your csv and abstractions, not trying to convince you that you should switch from whatever works for you.
The thing with simple tools is that bootstrapping is easy and versatile.
All that said, I wouldn’t touch Postman. Last time I needed something to fit this bill I looked around to find the open source equivalent and found Bruno.
Is there a way to send the json request that one sends in Postman but in curl while also using the jks file?
Similarly, we use SoapUI to send XML requests. Is there a way to send those XML requests using curl while also using the jks file?
Greatly appreciate your help.
I use curl liberally and also tend to create scripts around it to perform common tasks, but I still get why someone would prefer a GUI.
Just save your requests in separate script and organize them.
And now you can run them from anywhere, including other scripts
This is why, people do not want to bother with the docs.
Plain text file?
Works everywhere.
It could be a script or a markdown with code blocks. I believe there’s wrapper with a more codified formats like .http.
users/create.sh, users/delete.sh, etc
The page even sort of acknowledges this... saying you manage your environments with environment variables. It doesn't mentioned how to extract data from the response, just jq for syntax highlighting. No explanation of combining these two into any sort of cohesive setup for managing data through flows of multiple requests. No mention anywhere on the page of working with an OpenAPI spec... many of the tools provide easy ways to import requests instead of manually reentering/rebuilding something that's already in a computer-readable format.
So the tl;dr here is "use cURL, and then rebuild the rest of the functionality in bash scripts you idiot".
I went down this path of my own accord when Insomnia was no longer an option. I very quickly found myself spending more time managing bash spaghetti than actually using tools to accomplish my goals.
That's why I use a full blown dedicated API client instead of a HTTP client. (Not Postman though. Never Postman.)
Then it turned into a monstorsity.