Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards
- API access control (32)9.292%
- API user onboarding (22)8.989%
- API monitoring and logging (32)8.484%
- API versioning (24)8.383%
Leaving a video review helps other professionals like you evaluate products. Be the first one in your network to record a review of Postman, and make your voice heard!
Postman Free Plan
$0.00 US Dollars
Postman Basic Plan
$12 US Dollars
Postman Professional Plan
$29 US Dollars
Entry-level set up fee?
- No setup fee
- Free Trial
- Free/Freemium Version
- Premium Consulting / Integration Services
- Supported: API access control
- Supported: API versioning
- Supported: Usage billing and payments
- Supported: API monitoring and logging
Visit https://www.youtube.com/channel/UCocudCGVb3MmhWQ1aoIgUQw to watch Postman video.
- Simple to use and understand UI.
- Easy to integrate with release pipeline using Newman.
- A lot of online help available.
- Make it a little easier to share tests as one-off.
- bundling of APIs into collection
- allow to create a globally accessible link
- great UI/UX to interact with APIs
- desktop version is process heavy
- same is the case with extention
- it would be better if they produce a slim minimal version with only essentials packed in
it is very efficient when it comes to manage large number of APIs, one can manage APIs per project as well.
very good authentication testing UI. makes it pretty easy to work with all kinds of available AUTH practices.
allows to ingest multiple types of data like FORMDATA/JSON
- Postman API allows you to access data in your Postman account using code. Execute all of the standard CRUD operations on your collections, environments, mocks, and other objects.
- Postman used to be a platform where people worked alone and independently tested APIs. Working together has never been easier with features like commenting, forking, branching, pull requests, tagging, and more.
- Wherever you need to automate tests that involve database verification or rely on data from databases, Postman is less suitable.
- Postman's disc usage is extremely high, and it occasionally causes the computer to fade.
- It doesn't have the ability to generate random data. To achieve randomness in my tests, I've been working around scripts.
- Loading APIs (Just put the URL and hit send, if it doesn't require security token)
- N-level of organizing collections into folders/ sub-folders
- Sharing the collection across team
- Create documentation, adding examples for each scenario
- Run Feature
- Assertion scripts snippets are really helpful in tests
- Environments can be organized as per users' need.
- Database connectivity - To get data directly from DBs (traditional plus new like MongoDB or CosmosDB)
- Data Generator - Random data generator like email, names, zip/postal codes, addresses, mobile number. Although there's a public API but it has limits.
Postman is less appropriate where you need to automate your tests that involves verification from databases or depends on data from databases. Also, it lacks functionality to generate random data. I've been using work around using scripts to achieve randomness in my tests.
- Managing the created APIs in a flexible way
- Testing the APIs with GET, POST, PATCH, DELETE any many more requests
- Creating API documentations for future reference
- Disk usage of Postman is a lot high, sometimes it causes computer to flicker
- The UI of Postman can be made more cleaner
- API deployment services can also be added
- It helps with testing different services easily
- Load time of the application is very quick
- Useful product for making API calls
- It should allow for easier use when many tabs are open at the same time
- Sometimes loading the collections in JSON format is not easily done
- While testing SOAP APIs there is definitely some room for improving the user's experience
- Use to use, thanks to snippets and in line IDE.
- Quick test runner.
- Headless running in deployment pipeline.
- Autocomplete in IDE.
- Folderwise selection of Requests to run in test runner.
- Copying requests through drag'n'drop.
- Linking of requests to, so that not every copy has to be maintained.
- Get support.
- API testing
- API development
- Mock API services
- Dashboard View
- Updates are less frequent
- Simple and quick to create requests.
- Built in snippets for simple assertion generation.
- Externalizes parameters in environment files to allow simple swapping between development and test environments.
- The ability to integrate with a 3rd party source control system is frustrating. Needing to export a singular large raw file and store that in source control myself introduces a number of merge conflicts. Postman does offer their own source control system, but this does not allow me to parallelize my test code alongside my development code, and diverges from our development strategy.
- There [are] no elegant means of conditionally executing a particular step. Postman includes the ability to "go to" a request, but this requires looking deep into the implemented test or pre-request code to know that this behavior is present.
- There is no good solution to code reuse. I cannot define a particular request structure and parameterize it for future use. I am forced to replicate requests over and over and modify them all when changes are needed.
- Organize how to use an API
- Generate codes 'ready-to-use' for implementation
- Simulate API calls (for API development or test)
- Create process for data extraction via API
- Read paginated data
- Schedule requests
- Shared API connections.
- Building collection of API calls.
- So universal.
- Would be great to have "simple UI" for business users.
- It has opened a door for me to explore more out of it, as it is associated with so many APIs that I never felt any difficulty in finding the right API template, which are well organized and easily available.
- It is very secure to use and provides great services which are user-friendly.
- Due to this software I have got rid of the excessive emails and the slack channels, Now I am using my own private API and even it give me an option to produce my personal Postman’s API Builder from its Private API Network and this features has shared my excessive workload.
- It is quite technical and complicated too.
- I think the reporting features needs to be modified so we won’t be able to miss important features.
- It does not tackle efficiently the SOAK APIS and it is limited in the area testing as well.
- API TESTING
- API PRODUCTION MODE TESTING
- should not save every call
- UI is good but need little improvement
There is not any major issue i have detected in postman while using.
- Ease of access.
- Supports multiple header, raw data and param options.
- Response can also be visualized in different forms.
- Response code can be copied.
- Full API code can be imported in almost all major languages.
- Software stuck sometimes when there are lots of database API.
- Not so beginner friendly, I needed help when I first started to use Postman.
- Easy to configure, just point to the service URL and you're good to start.
- Easy to set up parameters on method calls.
- Limited reporting: it would be nice if we could export a log file of failed calls.
- Not a ton of automation: would be really useful for QA/integration testing.
- It has a group environment through which different teams can integrate and work together.
- Easy to switch between different modes i.e JSON XML. Authenticating using different protocols is easy.
- Pricing is also very comfortable.
- Enterprise version is easy to setup and use but the number of requests is limited. I feel it would be great if there were more requests.
- Pricing for enterprise should be less.
- I don't have any more complaints as it is very good tool.
- Easy to use
- Integration was possible everywhere I tried.
- Sharing option is limited between the team
- Its not possible to test more than 1 API simultaneously
- Execute HTTP requests seamlessly using a lightweight client.
- Configure HTTP request headers and body payloads easily.
- The user interface is complicated, especially when you need to dig into one of the many settings.
- I don't know where else Postman can perform better. So far, I haven't had many issues with Postman other than the learning curve.
- Submit API requests and view responses without the need for a browser or browser extensions.
- Archive and group API requests by type, application, or any way you see fit.
- The documentation produced is useful, but it could provide more information.
- Sharing the documentation could be made easier.
- Ability to store commands
- Integrates with Jenkins
- Faster bug fixes
- Fast API calls can be made for http protocol and restful service prospective.
- Free and open source tool.
- Tool has limited automation capability.
- Tool has limited report generation capability.
- Send Rest Request easily.
- Modify different types of parameters with ease.
- I hope they could develop a trace log like that of Apigee Edge where I could visually see what happened as the request gets processed.
- Add the auto Beatify or AutoCorrect formats of JSON texts.
- Intuitive interface - Postman's desktop client is well designed and easy to use.
- Collaboration - Coworkers can share a work space and work together from any location.
- Configuration - Postman offers hundreds of settings for extensive customization.
- Desktop based - While it's possible to run Postman on a phone or tablet, it works best on desktop environments.
- Data analysis - It would be helpful to be able to run more data analysis directly within the tool. Exporting isn't always as straightforward as it could be.
- Issue GET and POST calls to external APIs to verify headers and responses.
- Verify developed internal APIs.
- Build a library collection of useful API calls to be used as needed.
- The history of previous calls is easily searched to pull up calls to be modified and repeated.
- It is difficult to move a folder from one collection to another.
- It may be necessary to subscribe to the professional edition to get needed functionality. So far, I have been able to use the free edition to do a substantial amount of work. For example, sharing with teams with large collections would require the paid edition.
- Switching from team back to individual may result in lost collections that were archived. Export the archive before you do this so you can import it. this area can be confusing.
Collections of calls can be shared with teams for effective collaboration.
If your application has some sort of error in the API call, use the browser developer tool (generally F12) to view the call and response in the Network tab. Reproduce the call in Postman to reproduce the unexpected result. Fix your application and re-test with Postman. Iterate until the application behaves as it should.
- It allows us to share API calls.
- Easy to create test API calls.
- Easy to install.
- Easier to share to non-workspace users.