How Postman Grew From a Chrome Extension to a Developer Standard

How did Postman grow from a Chrome extension to a developer standard?

Postman grew by winning individual developers first, through a free tool in the Chrome Web Store, and then building the team, partner and public features that turned a personal habit into shared infrastructure.

Contrary Research and YourStory agree on the start: a developer built an API tool for his own use, listed it in the store and saw adoption arrive before any company existed. They differ on dates and user counts, which is why each figure below carries its source and date.

• Distribution came before the company: a Chrome Web Store listing and a Stack Overflow reply produced the first adoption, per Contrary Research.
• Payment came by request: YourStory reports a donate button and an unprompted $500 cheque from a company that had no other way to pay.
• The tool spread to teams through collections, workspaces and integrations, as Contrary Research describes them.
• User counts run from 11 million (YourStory, July 2020) to 25 million (Contrary Research, early 2023), and all of them are company claims.
• The sources contain no Postman revenue, so revenue growth is outside this page.

Where did Postman start, and when?

Postman began as a side project by Abhinav Asthana to fix his own difficulty testing and debugging APIs, which YourStory dates to 2012 and Contrary Research places before the company's formal 2014 launch.

Contrary Research says Asthana met Ankit Sobti during a 2012 internship at Yahoo in Bangalore, where both kept hitting the same wall: no tools existed to implement and debug APIs, and each API update meant starting over. After leaving his first company, TeliportMe, and taking consulting work, Asthana met the same problem again, found no tool that fit, and spent a weekend building a basic HTTP client for Chrome.

YourStory adds what he noticed once TeliportMe was behind him. In his telling, Postman already had what he had tried to build deliberately in earlier products: users who loved it, a community forming around it, and people recommending it as part of their daily workflow.

The dates need care. YourStory says the company was formally started in late 2014 and Contrary Research says the trio of Asthana, Abhijit Kane and Sobti launched it in 2014, but neither gives the day the first Chrome version went live. The sources support a 2012 side project and a 2014 company, and nothing more precise.

How did the Chrome Web Store and Stack Overflow seed adoption?

Contrary Research credits two acts of distribution for Postman's first wave: listing the open-source tool in the Chrome Web Store, and answering a Stack Overflow question about APIs with a link to it.

That report says the tool passed 2,000 downloads within days. The Chrome team in the Bay Area then invited Asthana to feature Postman among the top apps on its new app platform, which it was positioning against native apps, and he rewrote the tool for it.

YourStory tells the same arc in fewer details: Chrome developers liked the app, featured it on the store, and its popularity multiplied. Asthana's co-founders joined after that, and the three launched the company in 2014.

Our reading, labelled as inference: the sequence was a marketplace with built-in discovery, a question already being asked in public, and a platform owner that wanted showcase apps. The sources do not say how many early users came from Stack Overflow and how many from the store, so the split is unknown.

How did a free tool become a business?

Postman became a business after users asked to pay: YourStory reports a donate button on the tool and a Seattle company that sent a $500 cheque because it wanted to pay and had no way to.

That is the strongest demand evidence in the sources, because money was offered before any price existed. Treat it as one data point from one company, reported by a journalist from the founder's account.

Asthana also describes how he ran the product. He says the bug tracker is open, the features that exist are on the website, the ones that do not sit on the issue tracker, and the team listens to its community constantly.

He argues that competitors could copy the product but would trail it within a week, because Postman keeps listening and updating. That is an argument from the founder, not a measured result.

Fundraising followed adoption. Asthana told YourStory that Postman never pitched investors: they called after hearing that companies in their portfolios used it, and he skipped the deck, pointing instead to half a million users, the store's top rating in developer tools, and recommendations from Microsoft, Bosch and other developers.

How much did Postman raise, and how fast did its valuation rise?

YourStory's July 2020 article lists four rounds totalling $208 million: $1 million, $7 million, $50 million and $150 million, the last at a $2 billion valuation.

The article gives round dates relative to its own publication, so the table converts them. A “last month” in a July 2020 article is June 2020, and “June last year” is June 2019.

$1M + $7M + $50M + $150M = $208M raised through the Series C

YourStory also says the company had not disclosed valuations for earlier rounds and estimates about $350 million at the Series B. On that estimate the jump to $2 billion is 2,000 / 350, or about 5.7 times, an increase of (2,000 - 350) / 350 = 471%, which the article rounds to nearly 500 percent.

Because the Series B valuation is an estimate, the multiple is one too. The same article says Postman went from formal start to unicorn status in under six years.

Later numbers are loose. Everstage's customer page calls Postman a company valued at $5.6 billion without naming a round or a date, and a search-result title from a data aggregator lists $433 million raised, but that page was not extracted. This article uses neither as a funding fact.

How many users does Postman have, and can the numbers be compared?

Postman's user claims run from 11 million developers in July 2020 to 25 million in early 2023, but the sources use different units and dates, so they cannot be lined up as one growth curve.

The units clash inside a single source. Contrary Research reports about 26 million developers worldwide at the end of 2022, and also says 25 million developers use Postman and that 53% of Postman users in 2023 were not developers.

Our reading: 25 million out of 26 million would be about 96% of all developers, and that cannot be literal if more than half of users are not developers. The headline numbers most likely count accounts or registered users, though no source says so.

Taken at face value, 25 million against 11 million is 2.3 times in roughly two and a half years, but that compares two different sources. The practical lesson for a founder is to define your own user metric and date it before quoting it.

What does developer-led growth mean in Postman's case?

That is Kanso's working definition, not one taken from a source. Postman's documented path shows three markers of it.

1. Adoption happened without a sales conversation: the Chrome listing and the Stack Overflow link did the work, per Contrary Research.
2. Recommendation travelled between developers and into companies: investors heard about it from portfolio companies, and Microsoft and Bosch developers recommended it, per YourStory.
3. The company layer came afterwards: team and partner workspaces, a private API network and a sales force, per Contrary Research and Everstage.

Search results for the term include guides from WorkOS and daily.dev. The research package holds only their titles, so this article does not summarise them.

How did Postman turn a personal tool into a team standard?

Postman turned a personal tool into a team standard by adding shared containers for the work: collections for requests, then workspaces for personal, team, partner and public use.

Contrary Research describes collections as groups of requests that can be reused, can carry JavaScript to chain requests together, and can be run from the command line through Newman inside CI/CD pipelines. Documentation can be generated from the Collection format, and mock servers can simulate an API before it ships, so one artifact serves several stages of API work.

The report counts over 30 integrations as of January 2024 and names GitHub, Slack and APIMatic among them. The table below sets out the four workspace types it describes.

Read together, the four types widen the circle of use from one person to colleagues, then to partners, then to anyone. That widening is our interpretation of the table; the report describes the types but does not call them a growth ladder.

Which network effects does the evidence support?

The evidence supports a publishing effect around public workspaces and a collaboration effect around shared ones, but no source measures either as a result.

Contrary Research says public workspaces are searchable through the Public API Network, and that organisations use them to gather feedback, onboard developers and show their APIs. As of the end of 2023 it also reports Postman's own claim to host the largest public API collection on the internet.

The mechanism we infer: each company that publishes an API there gives developers a reason to open Postman, and gives that company's own users an on-ramp into it. No source reports how many signups arrive this way, so treat it as a plausible loop, not a proven one.

The collaboration side has a different kind of support. Postman's 2025 State of the API report, a survey of over 5,700 people, says 93% of teams struggle with API collaboration and only 7% report none of the listed problems. Postman sells collaboration tooling, so the survey is evidence of the pitch it makes as much as of the pain.

What did Postman's enterprise motion look like?

The enterprise motion visible in the sources is a sales organisation and a governance layer added on top of bottom-up adoption, not a replacement for it.

YourStory reports, as company claims in July 2020, over 500,000 companies including Microsoft and Twitter, and use by 98% of the Fortune 500. Contrary Research repeats the 98% figure for 2023. No source defines what counts as use, so one account in one large company may be enough to qualify.

Contrary Research also describes a Private API Network with versioning and folder structure for larger organisations, and notes that enterprises of more than 10,000 employees can run over 25,000 APIs. That is the problem a governance product addresses.

Everstage's undated customer story says Postman's sales force grew 300% after the two companies began working together, and that the sales team's commission plans were becoming more complex. It is a vendor's account of its own customer, and the partnership date is not given, so it shows that a sales layer exists but not when it started.

What was Postman's marketing, channel by channel?

The sources show Postman's marketing as a set of developer channels, each tied to a product feature or a community act, and document no paid programme.

The table below was built by taking each channel a source names in the three reports and the 2025 survey, recording what that source says and when, and adding a separate inference column. A channel appears only if a source documents it, and the last column is Kanso's interpretation.

What the table cannot hold is spend. No source gives a marketing budget, paid channel, event programme, developer-relations headcount or conversion rate, so none is claimed.

Which of Postman's moves can a dev-tool founder reuse, and when?

A founder can reuse a Postman move when the condition that made it work is also true for their product, and the table below states each condition as a question to answer first.

The framework was built from the channel table above: each row pairs a stage with the documented move and a check. The checks are our judgment, not findings from any source.

Two other developer-facing growth stories on this site show different channels doing similar work: how Razorpay grew with developers through documentation and integrations and how Stripe's documentation doubles as marketing.

For the Stack Overflow style of seeding, the question-venue rules differ by site, and when to post, comment or stay out on Hacker News covers one such venue. A founder planning the first months can pair this with a week-by-week 90-day plan for technical founders.

What is documented, and what is our analysis?

Documented facts are statements a named source makes; analysis is Kanso's interpretation of them, and the two are listed separately here so a reader can tell which is which.

Documented, with the source in each item:

• The tool was open source, listed in the Chrome Web Store, and shared in a Stack Overflow reply (Contrary Research).
• The Chrome team invited the founder to feature it on the new app platform (Contrary Research).
• A donate button existed, and a Seattle company sent a $500 cheque (YourStory).
• Seed, Series A, Series B and Series C amounts and leads (YourStory, July 2020).
• Four workspace types and over 30 integrations as of January 2024 (Contrary Research).
• The survey figures from the 2025 State of the API report (Postman).

Analysis, which no source states:

• The Stack Overflow link and the store listing worked as separate seeding channels whose split is unknown.
• The 25 million developer figure counts accounts, since over half of 2023 users were not developers.
• Public workspaces create a publishing loop between API owners and developers.
• The four workspace types work as a ladder from one person to anyone.
• The 98% Fortune 500 claim means at least one user in the company.

What do the sources not tell us about Postman's growth?

The sources do not give Postman's revenue, marketing spend, conversion rates, pricing history, or any funding after the 2020 Series C, so this page makes no claim on those.

The research found one SEC filing when searching for a Postman annual report, but it is the 10-K of an unrelated company, so none of its figures appears here. Third-party revenue estimates showed up in search results and were not read.

Postman's own post, How We Built Postman - the Product and the Company, ranks first for the topic, and the research holds only its search snippet. Anyone building on this page should read that post and the State of the API archive for earlier years before relying on any user figure.

Frequently asked questions about Postman's growth

Sources

• Report: Postman's Business Breakdown & Founding Story, Contrary Research
• The untold story of Postman CEO who built a $2B startup, YourStory, July 2020
• Postman | Customer Stories, Everstage (undated)
• 2025 State of the API Report, Postman
• How We Built Postman - the Product and the Company (search snippet only), Postman Blog