The Postman Story: How a Side Project Transformed API Testing
How Postman began as a free Chrome side project in 2012 and grew into the API platform used by tens of millions of developers, reshaping how APIs are built and tested.
Plenty of billion-dollar tools began as something an engineer built to scratch their own itch. Postman is one of the clearest examples: a free Chrome extension made to simplify a repetitive, annoying task, API testing, that grew into a platform used by tens of millions of developers. Here is how it started and how it reshaped the way software teams work with APIs.
Last checked: November 1, 2026. This is a developing story; check official sources for the latest status.
The problem: APIs were painful to work with
An API (application programming interface) is how one piece of software talks to another, the plumbing behind almost everything online. But a decade and a half ago, testing and debugging APIs was clumsy. Developers cobbled together command-line tools and scripts, repeated the same requests by hand, and had no easy way to save or share their work. The task was essential and endlessly repetitive, exactly the kind of friction that invites a better tool.
According to the company's own account, the seeds were planted earlier, at Yahoo Bangalore, where future co-founders worked on turning APIs into shareable formats and kept running into the same problems.
How it started: a free Chrome extension in 2012
In 2012, Abhinav Asthana built Postman as a side project to simplify API testing and offered it free in the Chrome Web Store. The name is a neat play on the HTTP "POST" request, one of the fundamental ways software sends data to an API, so "Postman" delivers your requests.
Its appeal was immediate and practical: a clean interface to compose a request, send it, and read the response, without writing throwaway scripts. Developers could save requests, organize them, and come back to them later. That simple quality-of-life win spread by word of mouth through engineering teams.
From extension to company
The side project grew faster than a side project should. Asthana brought in co-founders Ankit Sobti and Abhijit Kane, and Postman, Inc. was formed to turn the tool into a business. What began as a single-purpose request tester expanded step by step into a platform covering far more of the API life cycle.
How Postman transformed API testing
Postman's impact goes well beyond a nicer interface. It changed the workflow around APIs in several lasting ways.
1. It made API work visual and approachable
By replacing raw command-line requests with a clear, visual tool, Postman lowered the barrier to working with APIs. Newcomers could learn by doing, and experienced developers moved faster.
2. It made requests shareable and repeatable
Collections, saved, organized groups of requests, meant a team could share a tested set of API calls instead of each person reinventing them. Tests became repeatable rather than one-off, which is the foundation of reliable software.
3. It expanded across the whole API life cycle
Over time Postman grew from testing into design, documentation, mocking, monitoring, and collaboration, aiming to support an API from planning through deployment. The company has said it hosts one of the largest public collections of APIs on the internet.
4. It helped normalize an "API-first" way of building
As APIs became the backbone of modern software, Postman's popularity both reflected and reinforced the idea that teams should design and test APIs deliberately, not as an afterthought.
Where AI fits now
Postman's current chapter leans into AI, which is likely what you have heard about. As software increasingly consists of services talking to each other through APIs, those same APIs are what AI systems and agents call to get things done. Tooling that helps developers design, test, and manage APIs is therefore becoming part of how teams build and validate AI-driven features. If you are exploring AI tools more broadly, see our guide to the best AI tools that actually save time.
Lessons from Postman's rise
Pros
- Solved a real, repetitive developer pain point
- Free and frictionless to adopt (Chrome extension)
- Made API work visual, shareable, and repeatable
- Grew with its users across the whole API life cycle
Cons
- As it expanded, it became far more than a simple tester
- Breadth can feel heavy for someone who just wants to send one request
- Enterprise features and pricing evolve; confirm current details
Who should care about this story
- Developers and technical freelancers who work with APIs directly.
- Non-technical founders who want to understand the plumbing behind modern and AI-powered software.
- Anyone choosing tools, as a case study in how focused, free tools win adoption, a theme we explore in all-in-one vs separate tools.
Our verdict
Sources
Frequently asked questions
When did Postman start?
Postman launched in 2012 in Bangalore as a side project by software engineer Abhinav Asthana, who wanted to simplify API testing. It was first offered free as a Chrome extension in the Chrome Web Store.
Why is it called Postman?
The name is a play on the HTTP 'POST' request, one of the core methods used when sending data to an API. Postman lets developers send and inspect these requests easily.
Who founded Postman?
Abhinav Asthana started it as a side project and later co-founded Postman, Inc. with Ankit Sobti and Abhijit Kane. The founders had crossed paths earlier at Yahoo Bangalore.
How big is Postman now?
Postman reports being used by tens of millions of developers worldwide, with the company citing figures around 40 million. Exact numbers change over time, so confirm current figures on the official site.
Related reading
Best AI Tools for Freelancers: What Actually Saves Time
The best AI tools for freelancers that genuinely save time, from writing and admin to design and scheduling, with honest guidance on where AI helps and where it doesn't.
How to Choose Between All-in-One Freelance Software and Separate Tools
Should you use one all-in-one freelance platform or separate best-in-class tools? A clear framework to decide based on cost, workflow, and how you like to work.
The iLovePDF Story: How One Frustrated Task Simplified File Processing
How iLovePDF started in a Barcelona bedroom in 2010 and grew into one of the world's most-used PDF platforms, transforming how everyday people process files online.
The Zero-Budget Freelance Software Stack (Best Free Tools in Every Category)
Build a complete freelance software stack for free: the best no-cost tools for invoicing, accounting, time tracking, project management, security, and AI.