I occasionally use curl, and it’s annoying when you have secrets that need to rotate regularly or you need to change the middle of a URL. Also: Fuck quoting in the shell.
I put the secrets in environment variables, I don’t what them to show up in the shell history anyway. Quoting can be a bit anything if you need nested quotes, but I hardly ever need that with curl.
If you have decent documentation you shouldn’t need an api client. https://justuse.org/curl/
My evangelism has worked evil laughter
I occasionally use curl, and it’s annoying when you have secrets that need to rotate regularly or you need to change the middle of a URL. Also: Fuck quoting in the shell.
I put the secrets in environment variables, I don’t what them to show up in the shell history anyway. Quoting can be a bit anything if you need nested quotes, but I hardly ever need that with curl.
Well having decent documentation is kind of rare.
But is providing a special client for your api really less work than fixing your documentation?