![]() ![]() Handling auth in curl can be a real pain. This I think is where some of the power of postman really begins to shine (and tools like it). So postman has pretty rich support for a few auth types (api key, no auth, oauth 1.0 & 2.0, signatures, ntlm etc). You could use the openapi client generator to produce a curl command. As with a lot of this stuff, you /can/ do this without postman. Especially with the sharing capabilities which I'll touch on under the team side of things. Even as openapi/swagger docs on steroids with a richer http client this gets pretty powerful. ![]() This combined the the 'UI alternative to curl' really gives a lot of the foundational power for the other postman features. It's a pretty solid one, especially if you integrate with the API during your build process to version/upload the API specs. This will be the most commonly pointed at benefit of postman (and others like it) in my opinion. The ability to import openapi/swagger/protobuf (as of recently) and generate collections I'd say that the UI on top of curl is more accurately viewed as an alternative to things like jetbrains's build in http client. For folk not familiar with curl there's a lot of gotchas when it comes to escaping, handling auth, etc. For simple get/post requests, this is definitely the case. This is the most basic usage and a lot of the of other functionality is extensions of this. This is kind of expanding on koeffiezets comment.įor me postman's 'value add' can be broken down into three areas. With that said we use it pretty heavily so I might be able to provide some insights. I find the user experience to be counter intuitive compared to the likes of insomnia. To preface this, I'm not a massive fan of postman. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |