Need advice about which tool to choose?Ask the StackShare community!
From a StackShare Community member: "I just started working for a start-up and we are in desperate need of better documentation for our API. Currently our API docs is in a README.md file. We are evaluating Postman and Swagger UI. Since there are many options and I was wondering what other StackSharers would recommend?"
I use Postman because of the ease of team-management, using workspaces and teams, runner, collections, environment variables, test-scripts (post execution), variable management (pre and post execution), folders (inside collections, for better management of APIs), newman, easy-ci-integration (and probably a few more things that I am not able to recall right now).
I use Swagger UI because it's an easy tool for end-consumers to visualize and test our APIs. It focuses on that ! And it's directly embedded and delivered with the APIs. Postman's built-in tools aren't bad, but their main focus isn't the documentation and also, they are hosted outside the project.
I recommend Postman because it's easy to use with history option. Also, it has very great features like runner, collections, test scripts runners, defining environment variables and simple exporting and importing data.
OpenAPI is an excellent tool for creating interactive and hosted documents when releasing an API to the public. We will leverage this, specifically for the public facing APIs that customers can integrate into (to automate creating projects and storing experiment data). Postman is more complicated to share with others and is not as rich for documentation.
Postman supports automation and organization in a way that Insomnia just doesn't. Admittedly, Insomnia makes it slightly easy to query the data that you get back (in a very MongoDB-esque query language) but Postman sets you up to develop the code that you would use in development/testing right in the editor.
Pros of Postman
- Easy to use490
- Great tool369
- Makes developing rest api's easy peasy276
- Easy setup, looks good156
- The best api workflow out there144
- It's the best53
- History feature53
- Adds real value to my workflow44
- Great interface that magically predicts your needs43
- The best in class app35
- Can save and share script12
- Fully featured without looking cluttered10
- Collections8
- Option to run scrips8
- Global/Environment Variables8
- Shareable Collections7
- Dead simple and useful. Excellent7
- Dark theme easy on the eyes7
- Awesome customer support6
- Great integration with newman6
- Documentation5
- Simple5
- The test script is useful5
- Saves responses4
- This has simplified my testing significantly4
- Makes testing API's as easy as 1,2,34
- Easy as pie4
- API-network3
- I'd recommend it to everyone who works with apis3
- Mocking API calls with predefined response3
- Now supports GraphQL2
- Postman Runner CI Integration2
- Easy to setup, test and provides test storage2
- Continuous integration using newman2
- Pre-request Script and Test attributes are invaluable2
- Runner2
- Graph2
- <a href="http://fixbit.com/">useful tool</a>1
Pros of Runscope
- Great features17
- Easy to use15
- Nicely priced4
- Free plan4
- No install needed - runs on cloud2
- Decent2
- Collections1
- Dead simple and useful. Excellent1
- Awesome customer support1
- Import scripts from sources including Postman1
- Shareable Collections1
- Global & Collection level variables1
- Graphical view of response times historically1
- Integrations - StatusPage, PagerDuty, HipChat, Victorop1
- Run tests from multiple locations across globe1
- Schedule test collections to auto-run at intervals1
- Auto Re-run failed scheduled tests before notifying1
- Makes developing REST APIs easy1
- History feature - call history and response history1
- Restrict access by teams1
- Fully featured without looking cluttered1
- Can save and share scripts1
Pros of Shields.io
- Easiest way to create lovely badges4
- Easy & Awesome2
- Open source1
- Chef integration1
Sign up to add or upvote prosMake informed product decisions
Cons of Postman
- Stores credentials in HTTP10
- Bloated features and UI9
- Cumbersome to switch authentication tokens8
- Poor GraphQL support7
- Expensive5
- Not free after 5 users3
- Can't prompt for per-request variables3
- Import swagger1
- Support websocket1
- Import curl1
Cons of Runscope
Cons of Shields.io
Sign up to add or upvote consMake informed product decisions
What is Postman?
What is Runscope?
What is Shields.io?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Runscope?
What companies use Shields.io?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Shields.io?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+17