Postman

Score8.7 out of 10

478 Reviews and Ratings

Community insights

TrustRadius Insights for Postman are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.

Pros

Fast API calls: Many users have found the fast API calls feature to be very useful for HTTP protocol and restful service testing, with several reviewers mentioning its efficiency and time-saving capabilities.

Free and open-source tool: The fact that the software is a free and open-source tool has added to its appeal, as mentioned by multiple users. They appreciate the accessibility and affordability of the software.

Collaboration features: Several users have appreciated the ability to share API connections, create collections of API calls, and collaborate seamlessly with teammates. This universal feature of the software has been praised for enhancing teamwork and facilitating collaboration regardless of location.

Reviews

43 Reviews

Postman API tester

Rating: 8 out of 10

Incentivized

September 15, 2025

Use Cases and Deployment Scope

Postman is API testing tool which generates the request (like http) which hits the backend server and get the data from the database. Its a kind of checker between backend and frontend. As, i am in research department which aim to innovate more advanced technology and increasing functionality and reliability.

Pros

Debugging is easy to find and handle.
Data validation
Authorization checking
Automated monitoring

Cons

performnce slows down in large collections
security
Needs an improvement for advanced APIs

Likelihood to Recommend

Overall, Postman is the best API testing software with which you can assemble tasks easily, supporting multiple kinds of protocols with huge users across many platforms, such as Mac, Windows, Linux, and has collaborative features and authentication-based features, but is less appropriate for advanced APIs and a large set of data collections.

Verified User

Engineer in Research & Development (10,001+ employees)

Vetted Review

3 years of experience

One in a million Tool

Rating: 10 out of 10

Incentivized

March 7, 2025

Use Cases and Deployment Scope

Postman is really great and one of a kind tool for all our API's. We have all the API's there and working with it is really great.

Pros

API Testing
API Debugging

Cons

More API Calls

Likelihood to Recommend

i love working especially UI/UX and their courses which they offer to learn more about it. I personally store all the information there.

Verified User

Executive in Customer Service (11-50 employees)

Vetted Review

1 year of experience

Postman - Complete tool for API testing.

Rating: 10 out of 10

Incentivized

December 17, 2024

Use Cases and Deployment Scope

In our current business in my organization, we are moving from a legacy system to a new system with the latest cloud technology, and since everything is new, we are testing from scratch. Here, postman plays an important role in API testing. Managing collection through Postman is so easy that it makes testing comfortable.

Pros

API Testing and Debugging.
Environment management.
Variable management.
Automated Testing with Collections and Test Script.

Cons

I feel that good version control is missing.

Likelihood to Recommend

So, one of the significant and essential use cases for API is to test RESTful APIs during development; this gives early feedback in agile development without more test setups. It also supports writing test scripts in JavaScript to validate response data (status codes, headers, body). Mocking is also provided by API, which is important in agile development.

Verified User

Engineer in Engineering (201-500 employees)

Vetted Review

6 years of experience

Quick and interactive way to get set up with APIs

Rating: 8 out of 10

Incentivized

December 16, 2024

Use Cases and Deployment Scope

Postman helps us not only use APIs, but to save setups, workspaces, preferences, etc. This means we can adopt 'personas' when interacting with an API to test various use cases where certain permissions or roles are being used. Being able to share these workspaces and templates means people can publish and pull a standard setup for each type of API we work with.

Pros

Postman allows you to create unique workspaces = This means you can have one workspace for one vendor (E.g. GoogleMaps, Atlassian Marketplace etc.) or you can set up your workspace to be agnostic of vendor and instead use it as a 'persona' E.g. a local terminal, a service account on Airflow etc.
Sharing setups - Being able to share workspaces, settings, credentials, API calls and more means we can set up templates and distribute them to developers easily. It also means vendors can provide Postman templates to help get its users started.
Showing the API code that's generated - Postman is good at bringing a UI to what is essentially a terminal or code based set of instructions. Though this can mask what's actually going on behind the hood, there's an option to see what's actually being generated and cURL'd.
Visualise AI - Visualising the response of an API can be hard at times, however the integrated AI feature can help display the response in a table or graph. The table feature is particularly helpful for looking at non structured data in a structured way.

Cons

Postman can hide too much - Though the UI makes it easier to interact with APIs, it can sometimes what's happening behind the scenes. You can see what its' cURL'ing in some cases. But for some setups this isn't always enough.
Varying levels of settings and parameters - Postman is very customisable in terms of setting the scope of variables and credentials. This is very powerful, but can ultimately make it quite hard to see everything you need in one place. There are some times where a credential is being used or a variable is being grabbed from somewhere and I have no idea where it's coming from.
Postman nomenclature - Due to its complexity and customisability Postman uses a lot of its own nomenclature and naming conventions. Workspaces, environments, collections etc. It can be a bit overwhelming at the start and navigating the different layers with the new names to understand can mean getting set up can be slow.

Likelihood to Recommend

Postman is good for organising your API credentials, vendor settings, environments etc. It's also a good way of getting stared with APIs as you get to use a GUI which can help you understand what we mean by a 'body' or 'bearer token'. I think people generally gravitate towards GUI tools for getting started in a new technology area.

Callum O'Connor

Senior Analytics Engineer in Corporate at Adaptavist (501-1000 employees)

Vetted Review

1 year of experience

Verified on LinkedIn

Time saver of engineers

Rating: 10 out of 10

Incentivized

October 9, 2022

Use Cases and Deployment Scope

Postman just solves all the problem that developers had with the uses of API builidng and testing. It is baically an end to end solution for API. We can build and test it. Earlier it was so difficult to debug an API and now it is so easy. Earlier we had to write code and send the request and then see the response and then debug but with the development of this app, it has become so easy. It is saving a lot of engineering hours and I will recommend all Organizations to use it.

Pros

API Building
API Debugging
API Testing

Cons

API docs UI can be imporved

Likelihood to Recommend

It is well suited for all engineering scenarios. Any engineering organization which has API in use should use this without any hesitation. If you are building an API ? use it. If you are testing an API ? use it. If you are debugging an API ? use it. Use it for an end to end API development.

Verified User

Professional in Engineering (1001-5000 employees)

Vetted Review

2 years of experience

Postman the all-around best and simplest to use API tool

Rating: 9 out of 10

Incentivized

July 29, 2022

Use Cases and Deployment Scope

We use Postman to test and automate any new API's that we are creating, we have created full suites of automated scripts, which has allowed us to speed up testing in key areas. It also allows developers to run a test when needed to improve the quality of the overall work while at the same time reducing the time needed to test things.

Pros

Simple to use and understand UI.
Easy to integrate with release pipeline using Newman.
A lot of online help available.

Cons

Make it a little easier to share tests as one-off.

Likelihood to Recommend

Postman is easily one of the best tools for API testing, there is a lot to it and best of all there is a free version of the software, you can build out security test's as well as long as you know what you are doing with it, the only thing I can think of where it might not be appropriate is if you are not doing anything with API's. It doesn't allow any testing of any UI, just API's, so you will still need other tools to ensure full coverage.

Paul Alexander

Senior Test Engineer in Research & Development at Sage (10,001+ employees)

Vetted Review

3 years of experience

all in one tool AKA Swiss army knife of API world

Rating: 10 out of 10

Incentivized

July 15, 2022

Use Cases and Deployment Scope

The regular use case Postman is fine as it's helpful to manage multiple APIs belonging to various projects. but for our case, Postman is a big relief, especially because we often have to communicate with non-conventional clients who have their own custom API-consuming mechanisms. i.e SAP service; those guys do not possess familiarity with convention REST APIs. this is where Postman proved to be a big help. all we needed from our side was just give a link and they'll get the whole API collection.

Pros

bundling of APIs into collection
allow to create a globally accessible link
great UI/UX to interact with APIs

Cons

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

Likelihood to Recommend

if you have a small number of APIs to work with, it's probably an overkill
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

Lankit Patel

AWS Developer | Laravel Developer in Information Technology at AeonX Digital Solutions (51-200 employees)

Vetted Review

4 years of experience

View profile

Postman Review

Rating: 10 out of 10

Incentivized

May 24, 2022

Use Cases and Deployment Scope

Postman is what we use to test our API systems. We have a variety of public and private API systems, all of which are tested by my team using Postman. We've created separate collections for each, such as Smoke tests, which we run at each test deployment and Functional tests. These tests are continually updated (collection). My issue is that it lacks database connectivity, either relational or trendy-document databases like MongoDB. I have no choice but to export data from these databases and feed it into Postman. This is the only manual step a user must take; the rest of our tests are entirely automated.

Pros

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.
In the Pre-request and Test script tabs of Postman, you can use a set of external libraries. These libraries make life easier for developers by providing functionality that isn't always available in JavaScript.

Cons

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.

Likelihood to Recommend

When dealing with a collection of requests, it's common to run them in the order they were received. Other times, skipping or repeating certain requests is beneficial. The mailman arrives. The method SetNextRequest. You can programmatically choose which requests run and in what order by using conditional logic in the Pre-request or Tests tabs.

Verified User

Engineer in Customer Service (201-500 employees)

Vetted Review

2 years of experience

Except Data Generator and Database connectivity, happy with Postman

Rating: 10 out of 10

Incentivized

April 28, 2022

Use Cases and Deployment Scope

We're using Postman for testing of our API systems. We've got many different API systems, public and private, and all those systems are tested by my team using Postman. We've created different collections for each, as Smoke tests, that we run at each test-deploy and then we also have Functional tests collection. We're continuously maintaining these tests (collection). The problem I've is that it lacks the connectivity with databases, either relation or trendy-document DB like MongoDB/ CosmosDB. I have to rely on exporting data from these DBs and to feed it in Postman. This is the only manual step a user has to perform, otherwise our tests are based fully on automation.

Pros

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.

Cons

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.

Likelihood to Recommend

Postman is well suited where APIs are involved. I've been testing many backend systems and are well organized into many tests like Smoke for each system and then functional tests as well. Along with that I've few created monitors for production-critical endpoints/API-methods.

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.

Haroon Akmal

Sr. QA Engineer in Information Technology at Synergy-IT Pakistan (51-200 employees)

Vetted Review

5 years of experience

View profile

A must-have tool for API development

Rating: 9 out of 10

Incentivized

March 15, 2022

Use Cases and Deployment Scope

Being an IT Company, our organization was in need of an API testing and management tool. It had been a lot of hard to maintain APIs that connect the backend and frontend of our applications. Postman helped our company to manage and test the existing APIs as well as has been helping us to create new APIs. With the help of API documentation feature of Postman, it has been easy to provide guide to our clients within few clicks.

Pros

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

Cons

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

Likelihood to Recommend

Postman is best suited for the web and application development companies in which we constantly need to create APIs and test them. It is less appropriate for Graphic designing firms, animation companies and other companies that don't need to create APIs.

Bimal Subedi

Web Developer in Information Technology at Global Panacea Pvt. Ltd. (1-10 employees)

Vetted Review

3 years of experience

View profile

Loading Reviews List....

Quick and interactive way to get set up with APIs

Rating: 8 out of 10

Incentivized

December 16, 2024

Use Cases and Deployment Scope

Pros

Postman allows you to create unique workspaces = This means you can have one workspace for one vendor (E.g. GoogleMaps, Atlassian Marketplace etc.) or you can set up your workspace to be agnostic of vendor and instead use it as a 'persona' E.g. a local terminal, a service account on Airflow etc.
Sharing setups - Being able to share workspaces, settings, credentials, API calls and more means we can set up templates and distribute them to developers easily. It also means vendors can provide Postman templates to help get its users started.
Showing the API code that's generated - Postman is good at bringing a UI to what is essentially a terminal or code based set of instructions. Though this can mask what's actually going on behind the hood, there's an option to see what's actually being generated and cURL'd.
Visualise AI - Visualising the response of an API can be hard at times, however the integrated AI feature can help display the response in a table or graph. The table feature is particularly helpful for looking at non structured data in a structured way.

Cons

Postman can hide too much - Though the UI makes it easier to interact with APIs, it can sometimes what's happening behind the scenes. You can see what its' cURL'ing in some cases. But for some setups this isn't always enough.
Varying levels of settings and parameters - Postman is very customisable in terms of setting the scope of variables and credentials. This is very powerful, but can ultimately make it quite hard to see everything you need in one place. There are some times where a credential is being used or a variable is being grabbed from somewhere and I have no idea where it's coming from.
Postman nomenclature - Due to its complexity and customisability Postman uses a lot of its own nomenclature and naming conventions. Workspaces, environments, collections etc. It can be a bit overwhelming at the start and navigating the different layers with the new names to understand can mean getting set up can be slow.

Likelihood to Recommend

Callum O'Connor

Senior Analytics Engineer in Corporate at Adaptavist (501-1000 employees)

Vetted Review

1 year of experience

Verified on LinkedIn