Companies Using Postman API Documentation
Our live crawl finds Postman API Documentation on 6,068 domains in the August 2026 rollup, and 5,144 of them, 84.8%, resolve to an identifiable organisation. The companies using Postman API documentation named further down include Deloitte, Infosys, PwC, Marriott, Citigroup, Starbucks, UPS, Ford, AXA and SAP. Postman sells an API development platform, and this page counts two of its visible traces: a verified Postman workspace, and published API docs generated by the product.
What puts most of these domains on the list is a DNS TXT record, postman-domain-verification, published once to prove control of a domain when an account is set up. 8 of 8 domains we sampled still carry a live record. That marker is precise about one thing and silent about another: it proves an account existed, and it never expires, so it cannot tell you whether anyone opened the workspace this year. Three install clauses sit beside it, a generator: Postman Documenter meta tag, a PostmanRunObject JavaScript global and a Postman script host, which is why 3.4% of detections sit off the apex domain on documentation subdomains, against 0% on the IBM Cloud profile and 0.2% on its Docker equivalent.
The population behind those records is a developer one, and the size table says it without interpretation. 11-50 employees is the largest band at 1,826 of the 5,116 companies that report a headcount, 35.69%, 1-10 adds another 1,018 at 19.9%, and 2,844 of those companies, 55.59%, employ fewer than 50 people. Only 162 of the 6,068 domains, 2.67%, belong to companies of 8,000 or more. Software Development leads the industry mix at 1,276 of 5,063, 25.2%, and 3,555 of the 4,334 companies with a founding year on file, 82.03%, were founded in 2000 or later.
Geography spreads further than the size table alone would suggest. The United States holds 2,146 of the 5,006 companies we could place, 42.87%, then the United Kingdom at 7.97%, Brazil third at 4.63% and India sixth at 3.74%, with 1,003 located companies, 20.04%, outside the fourteen countries charted. This row ranks 4th in Documentation & Knowledge Base on 3.49% share. Below you can filter the websites using Postman API documentation by size, country, industry and co-installed technology. Data current to our August 2026 rollup.
Published Sep 8, 2026 · Updated Sep 8, 2026 · Data analysed on September 8, 2026.
Postman API Documentation Usage Statistics
We read 5,330 domains on the June 2026 rollup, 5,991 in July and 6,068 in August. Three points cannot carry a growth rate, and this movement is coverage rather than adoption. Across the whole crawl, active detections went from 321.0M in June to 352.2M in August, a 9.7% widening of what we can see. The marker makes the point sharper than usual: most of these matches are a DNS TXT record that was published once and never removed, so a domain entering this series means we resolved its DNS for the first time, not that a team signed up in July. A rising line here is our coverage catching up with a population that was already there. The August figure, 6,068, is the one quoted at the top of this page.
List of Companies Using Postman API Documentation
Download all 6,068 Postman API Documentation customers with full company data, or create a signal to track when companies start or stop using Postman API Documentation.
| Company | Detection URL | Domain | Country | Industry | Employees | Type | Founded | |
|---|---|---|---|---|---|---|---|---|
| deloitte.com | deloitte.com | United States | Business Consulting and Services | 10001+ | Privately Held | 1900 | https://linkedin.com/company/deloitte | |
| infosys.com | infosys.com | India | IT Services and IT Consulting | 10001+ | Public Company | 1981 | https://linkedin.com/company/infosys | |
| pwc.com | pwc.com | United Kingdom | Professional Services | 10001+ | Privately Held | 1998 | https://linkedin.com/company/pwc | |
| marriott.com | marriott.com | United States | Hospitality | 10001+ | Public Company | 1927 | https://linkedin.com/company/marriott-international | |
| citigroup.com | citigroup.com | United States | Financial Services | 10001+ | Public Company | 1812 | https://linkedin.com/company/citi | |
| starbucks.com | starbucks.com | United States | Retail | 10001+ | Public Company | 1971 | https://linkedin.com/company/starbucks | |
| ups.com | ups.com | United States | Truck Transportation | 10001+ | Public Company | 1907 | https://linkedin.com/company/ups | |
| ford.com | ford.com | United States | Motor Vehicle Manufacturing | 10001+ | Public Company | 1903 | https://linkedin.com/company/ford-motor-company | |
| axa.com | axa.com | France | Insurance | 10001+ | Public Company | — | https://linkedin.com/company/axa | |
| sap.com | sap.com | Germany | Software Development | 10001+ | Public Company | 1972 | https://linkedin.com/company/sap |
Show 24 more Postman API Documentation using companies as demo data
| Company | Detection URL | Country | Industry | Employees | Type | Founded | ||
|---|---|---|---|---|---|---|---|---|
| uber.com | uber.com | United States | Internet Marketplace Platforms | 10001+ | Public Company | 2009 | https://linkedin.com/company/uber-com | |
| cvshealth.com | cvshealth.com | United States | Hospitals and Health Care | 10001+ | Public Company | 1963 | https://linkedin.com/company/cvshealth | |
| subway.com | subway.com | United States | Restaurants | 501-1000 | Privately Held | 1965 | https://linkedin.com/company/subway | |
| pfizer.com | pfizer.com | United States | Pharmaceutical Manufacturing | 10001+ | Public Company | 1848 | https://linkedin.com/company/pfizer | |
| medtronic.com | medtronic.com | United States | Medical Equipment Manufacturing | 10001+ | Public Company | 1949 | https://linkedin.com/company/medtronic | |
| cisco.com | cisco.com | United States | Software Development | 10001+ | Public Company | 1984 | https://linkedin.com/company/cisco | |
| spectrum.com | spectrum.com | United States | Telecommunications | 10001+ | Public Company | 1993 | https://linkedin.com/company/spectrum | |
| loreal.com | loreal.com | France | Personal Care Product Manufacturing | 10001-10001 | Public Company | 1909 | https://linkedin.com/company/lor%c3%a9al | |
| calstate.edu | calstate.edu | United Kingdom | Higher Education | 11-50 | Educational | — | https://linkedin.com/company/the-california-state-university | |
| fidelity.com | fidelity.com | United States | Financial Services | 10001+ | Privately Held | 1946 | https://linkedin.com/company/fidelity-investments | |
| costco.com | costco.com | United States | Retail | 10001+ | Public Company | 1983 | https://linkedin.com/company/costco-wholesale | |
| slb.com | slb.com | United States | Technology, Information and Internet | 10001+ | Public Company | 1926 | https://linkedin.com/company/slbglobal | |
| danone.com | danone.com | France | Food and Beverage Manufacturing | 10001+ | Privately Held | 1919 | https://linkedin.com/company/danone | |
| pmi.com | pmi.com | Switzerland | Manufacturing | 10001+ | Public Company | 2008 | https://linkedin.com/company/insidepmi | |
| mercadolibre.com | mercadolibre.com | Argentina | Internet Publishing | 10001-10001 | Privately Held | 1999 | https://linkedin.com/company/mercadolibre | |
| zurich.com | zurich.com | Switzerland | Insurance | 10001+ | Public Company | 1872 | https://linkedin.com/company/zurich-insurance-company-ltd | |
| fisglobal.com | fisglobal.com | United States | IT Services and IT Consulting | 10001+ | Public Company | 1968 | https://linkedin.com/company/fis | |
| progressive.com | progressive.com | United States | Insurance | 10001+ | Public Company | 1937 | https://linkedin.com/company/progressive-insurance | |
| desjardins.com | desjardins.com | Canada | Banking | 10001+ | Privately Held | 1900 | https://linkedin.com/company/desjardins | |
| mtn.com | mtn.com | South Africa | Telecommunications | 10001+ | Privately Held | 1994 | https://linkedin.com/company/mtn | |
| adobe.com | adobe.com | United States | Software Development | 10001+ | Public Company | 1982 | https://linkedin.com/company/adobe | |
| chubb.com | chubb.com | Switzerland | Insurance | 10001+ | Public Company | 1882 | https://linkedin.com/company/chubb | |
| aetna.com | aetna.com | United States | Wellness and Fitness Services | 10001+ | Public Company | 1853 | https://linkedin.com/company/aetna | |
| bcg.com | bcg.com | United States | Business Consulting and Services | 10001-10001 | Partnership | 1963 | https://linkedin.com/company/boston-consulting-group |
There are 6,068 companies and domains where we detect Postman API Documentation, sign up to download the entire Postman API Documentation dataset.
Here are some of the most recognisable companies using Postman API Documentation and brands using Postman API Documentation in 2026, each with the domain the detection was found on:
- Deloitte Touche Tohmatsu Limited – business consulting group, detected on deloitte.com
- Infosys Limited – the highest-placed of the India detections, on infosys.com
- PwC – professional services firm recorded in the United Kingdom, on pwc.com
- Citigroup – company record dated 1812, on citigroup.com
- Marriott International – hospitality group, on marriott.com
- Starbucks Corp. – on starbucks.com
- United Parcel Service – recorded at 1907, on ups.com
- Ford – recorded at 1903, on ford.com
- AXA – French insurer, on axa.com
- SAP – the software development label in the named list, on sap.com
- Uber Technologies – recorded at 2009, on uber.com
- CVS Health Corporation – the health care detection in the named list, on cvshealth.com
All twelve are apex-domain matches, and all twelve sit in the 10001+ employee band that accounts for 3.42% of the 5,116 companies reporting a headcount. They are the visible tail of this population, not its centre.
Which Countries Use Postman API Documentation the Most?
Which countries use Postman API Documentation the most? The United States holds 2,146 of the 5,006 companies we could place, 42.87%, and the United Kingdom is second on 399, 7.97%. The interesting part is third: Brazil at 232 companies, 4.63%, ahead of Australia (196, 3.92%), Canada (193, 3.86%) and India (187, 3.74%), with Germany (141, 2.82%) and France (128, 2.56%) behind them. Netherlands 1.92%, Spain 1.5%, Singapore 1.12%, Mexico 1.08%, Switzerland 1.04% and Italy 0.96% fill out the chart. The fourteen countries shown cover 4,003 of the 5,006 located companies, 79.96%, which leaves 1,003 companies, 20.04%, outside them entirely, and 2,860 of the total, 57.13%, outside the United States. Named non-US detections match that spread: Infosys in India, PwC in the United Kingdom, AXA, Danone and L'Oréal in France, SAP in Germany, Zurich, Chubb and Philip Morris International in Switzerland, Desjardins in Canada, Mercadolibre in Argentina and MTN Group in South Africa.
Share of the 5,144 Postman API Documentation domains we matched to a company record — 84.8% of the 6,068 we detect. Top 14 countries shown, so these do not sum to 100%. Domains with no matching company record are not represented here and skew small and independent.
Postman API Documentation Market Share Among Documentation & Knowledge Base
What is Postman API Documentation's market share? It holds 3.49% of Documentation & Knowledge Base and ranks 4th in that category on 6,068 domains. Zendesk leads on 111,482 domains and 64.05%, then Foxit (8,700, 5.0%), MediaWiki (6,097, 3.5%), this row, Docusaurus (5,507, 3.16%) and Open Journal Systems (5,253, 3.02%). Two things to hold before quoting the rank. First, the gap between third and fourth is 29 domains, which is inside the month-to-month movement of a rollup this size, so treat 3rd and 4th as a tie. Second, the rows are not measured on the same surface: Zendesk help centres, MediaWiki and Docusaurus are read from the page a visitor loads, while 96.6% of the detections counted here are read from DNS at the apex domain. A share built that way counts domains carrying a detectable marker, not spending, seats or documentation traffic.
Top Competitors by Market Share
Postman API Documentation Customers by Company Size & Age
What size companies use Postman API Documentation? This is the table that defines the page. 11-50 employees is the largest band at 1,826 of the 5,116 companies that report a headcount, 35.69%, with 51-200 second at 1,028, 20.09%, and 1-10 third at 1,018, 19.9%. Added up, 2,844 companies, 55.59%, employ fewer than 50 people and 3,872, 75.68%, employ fewer than 200. At the other end, 585 companies, 11.43%, employ more than 1,000 and only 175, 3.42%, sit in the 10001+ band. Counted on domains rather than companies, 162 of the 6,068, 2.67%, belong to organisations with 8,000 or more employees. Read that against the named list further down, which is Deloitte, Infosys, PwC, Citigroup and Ford. Those names are real detections, but they are drawn from the 3.42% tail because the list is ordered by audience size, not by how typical a company is. The centre of this distribution is a team of fewer than fifty people.
Company Size Distribution
Company Age (Founded Decade)
The 2010s lead at 2,149 of the 4,334 companies with a founding year, 49.58%, and the 2020s add 756, 17.44%, so those two decades alone are 2,905 companies, 67.03%. Push the line back one decade and 3,555 companies, 82.03%, were founded in 2000 or later, leaving 779, 17.97%, that predate it. Pre-1960 is only 233 companies, 5.38%, and the 1960s bottom the chart at 38, 0.88%. That is the opposite shape to most enterprise software profiles, and it follows from what the record marks: a company verifies a domain when it opens an account, and the companies opening API tooling accounts skew young. The old names on the page are the exception that proves the tail exists, and the records behind them are long ones: Citigroup at 1812, Pfizer at 1848, Zurich at 1872, Chubb at 1882, Ford at 1903, UPS at 1907. One caveat on the recent buckets, as always: a founding year comes from the company record, and a restructured group can carry a later date than the business it descends from.
What Industries Use Postman API Documentation the Most?
Software Development leads at 1,276 of the 5,063 companies with a recorded industry, 25.2%, more than twice Financial Services in second at 587, 11.59%, with IT Services and IT Consulting third at 534, 10.55%, and Technology, Information and Internet fourth at 449, 8.87%. Group the related labels and the concentration is plain: software, IT services, internet, the separate Information Technology & Services label (161, 3.18%) and computer and network security (50, 0.99%) together are 2,470 companies, 48.79%, close to half the industry-tagged base. Money is the second cluster, with financial services, insurance (156, 3.08%) and banking (64, 1.26%) at 807 companies, 15.94%. Telecommunications (107, 2.11%), transport and logistics (101, 1.99%), health care (83, 1.64%) and advertising services (70, 1.38%) trail behind. The twelve labels charted cover 3,638 companies, 71.85%. Worth knowing before you quote a single row: IT Services and IT Consulting and Information Technology & Services are two labels for much the same thing and total 695 companies, 13.73%, between them.
Software companies using Postman API documentation are the single largest block at 25.2% of the 5,063 companies with a recorded industry, and that is the row doing the most work on this page: a software company publishes an API, an API needs documentation, and a workspace gets verified against the domain. SAP, Adobe and Cisco carry that label in the named list. Banks and insurers using Postman API documentation are the second cluster at 15.94% across three labels, and the reason is specific rather than general digital adoption: open banking and payments programmes publish partner-facing endpoints, and Citigroup, Fidelity Investments, Desjardins, AXA, Zurich, Chubb and Progressive all appear on their apex domains. Telecommunications at 2.11% and transport and logistics at 1.99% read the same way, with Spectrum, MTN Group and UPS on the list. Health care at 1.64% and advertising services at 1.38% are thin by comparison. One caution on the labels themselves: they come from the company record, not from us, and they are sometimes wrong at the row level. Schlumberger is filed here under Technology, Information and Internet, which is not what that business does. Use the clusters, not the individual rows.
Postman API Documentation Alternatives & Competitors
Documentation & Knowledge Base is a category whose members are counted on different surfaces, so the table needs reading twice. Zendesk leads on 111,482 domains and 64.05%, an order of magnitude clear of everything else, because a hosted help centre leaves a marker on every customer site that serves one. Foxit follows on 8,700 domains and 5.0%, then MediaWiki (6,097, 3.5%), this row (6,068, 3.49%), Docusaurus (5,507, 3.16%) and Open Journal Systems (5,253, 3.02%). The distance between third and fourth is 29 domains, so the ordering there is a coin flip on any given month. The comparison that actually matters is not the ranking but the mechanism: MediaWiki, Docusaurus and Open Journal Systems are self-hosted publishing software found in the page a visitor loads, Zendesk is a hosted service found the same way, and this row is mostly a DNS record proving an account exists. Those are not measurements of the same thing. A company can appear in this row and in a Docusaurus count at the same time, and roughly one detection in thirty here, 3.4%, is the only part read from a documentation site at all.
| Technology | Domains | Market Share |
|---|---|---|
Zendesk | 111,482 | 64.05% |
Foxit | 8,700 | 5% |
MediaWiki | 6,097 | 3.5% |
Docusaurus | 5,507 | 3.16% |
Open Journal Systems | 5,253 | 3.02% |
Postman API Documentation Customer Migration
There is no switching table here, and the reason is not that the corridors came back empty. They returned counts: 23 domains show a corridor from Zendesk into this row. We suppressed it because it fails the test we apply before publishing any migration figure, which is whether the two technologies do the same job for the same buyer. A hosted help centre serving support articles to customers is not a substitute for published API docs and a verified workspace, and the two are read off surfaces that cannot be lined up, one from the page and one from DNS. A domain that shows both signals has almost certainly changed neither. Publishing 23 as a switching trend would invent a story the data does not contain. The churn figure beside it needs the same discipline: 74 domains have dropped this detection since we began tracking in March 2026, 1.22% of the 6,068 counted here, and that number is close to meaningless as a retention signal. Nobody deletes a DNS TXT record when they stop using a product. Low churn here measures the persistence of the marker, not the loyalty of the customer.
Tech Stack of Postman API Documentation-Powered Websites
Read this table as a list of other things these companies have verified a domain against, not as what they run at request time. That is what a DNS-matched population produces: Google Workspace appears on 42.68% of these domains and Atlassian on 34.72%, both of which are themselves account markers rather than page signals, and Atlassian is absent from the table above only because we hold no icon for it. The rest divides into measurement and delivery. Google Tag Manager at 73.76% and Google Analytics at 71.14% are the marketing team's own tags. Cloudflare at 63.95% and Amazon Web Services at 35.09% are where the site is served from, and Google Font API at 53.98% and Priority Hints at 50.18% are ordinary front-end hygiene. The front-end rows are the only ones with a mild signal in them: Tailwind CSS at 38.74% sits above Bootstrap at 30.62%, which is not the ordering you see on a general population of company websites, and it is consistent with a base that is half software and IT firms. Treat it as consistent with, not proof of. What is notably absent is a vendor fingerprint. Nothing here sits at 99% the way a hosted platform's own build sheet does, because the marker is a DNS record and the website beside it is whatever the company happened to build. Co-occurrence is measured across the 6,247 domains our live crawl currently answers for, a slightly wider set than the 6,068 in the August rollup, so a percentage in this table divides by 6,247.
Verified SaaS Accounts on the Same Domains
Analytics & Tag Management
Cloud & Delivery
Front-End
Expert Analysis: Postman API Documentation Growth Trends & Key Signals for Sales Teams in 2026

This row counts two different things, and one of them is not usage
Four clauses feed this page, and they do not measure the same event. The one that fires most is a DNS TXT record, postman-domain-verification, which a company publishes once to prove it controls a domain when it opens a workspace. The other three read the page: a generator meta tag reading Postman Documenter, a PostmanRunObject global, and a script served from a Postman host. 8 of 8 domains we sampled carried a live TXT record, and 96.6% of all detections sit on the apex or www, which is where DNS resolves and nowhere else.
So the honest reading of 6,068 is this: it is the number of domains that have publicly verified a Postman workspace or are serving docs the product generated. It is not a headcount of teams using Postman today. A verification record has no expiry and no reason to be deleted, so every domain that ever completed that step stays in the count until someone tidies their DNS, which they do not.
The 3.4% of detections that sit off the apex are the interesting part, because they are the only ones reading actual published API docs. In the same batch, the two purely DNS-matched rows we published alongside this one, IBM Cloud and Docker, are at 0% and 0.2% off the apex. That small gap is the whole install-clause contribution to this page, and it is worth knowing it is small before you cite 6,068 as a documentation number.
A verification record proves an account existed. It does not prove anyone is using it, and it never expires.
One consolation for the reader: because a domain carrying a corporate DNS record is a real registered company, enrichment on this page is unusually good. 5,144 of the 6,068 domains, 84.8%, resolve to a company record, against roughly 46% on Amazon ALB. The count is soft about usage and hard about who the company is.
The named list is enterprise. The population is not.
Deloitte, Infosys, PwC, Marriott, Citigroup, Starbucks, UPS, Ford, AXA, SAP. Every organisation in the list further down employs more than ten thousand people, and every one of those detections is real. It is also completely unrepresentative, because the list is ordered by LinkedIn following, which sorts for fame rather than for typicality.
The distributions say something different. 11-50 employees is the largest size band at 1,826 of the 5,116 companies reporting a headcount, 35.69%, and 2,844 of them, 55.59%, employ fewer than fifty people. The 10001+ band, which is where all the famous names live, is 175 companies, 3.42%. Counted on domains instead, 162 of the 6,068, 2.67%, belong to organisations of 8,000 or more. Age agrees: 3,555 of the 4,334 companies with a founding year, 82.03%, were founded in 2000 or later, with the 2010s alone at 49.58%.
Industry closes the argument. Software Development is 1,276 of the 5,063 industry-tagged companies, 25.2%, and grouping it with IT services, internet and security takes the technology cluster to 2,470 companies, 48.79%. Nearly half this base builds software for a living. Geography matches: the United States is 2,146 of 5,006 located companies, 42.87%, but Brazil is third at 4.63% and India sixth at 3.74%, and 1,003 located companies, 20.04%, sit outside the fourteen countries charted altogether.
Small, young, technical, and spread across more countries than the buyer list suggests. That is a developer population, not a procurement one.
If you sell into this base, that distinction changes the target. The segment is not the 175 enterprises at the top of the visible list, it is the several thousand companies of under fifty people that make up the middle of it, and a meaningful share of them are outside the usual English-speaking set.
Rank 4 on 3.49% is a domain count across mismatched surfaces
This row holds 3.49% of Documentation & Knowledge Base and ranks fourth. Before that ordering gets quoted, two things need saying. The gap to third place is 29 domains, 6,068 against MediaWiki's 6,097, which is well inside what a monthly rollup moves. Third and fourth here are a tie, and next month they may trade.
The larger problem is that the category compares measurements taken off different surfaces. Zendesk leads on 111,482 domains and 64.05% because a hosted help centre leaves a signal on every customer site that serves one. MediaWiki (6,097), Docusaurus (5,507) and Open Journal Systems (5,253) are publishing software found in the page a visitor loads. This row is mostly a DNS record. One domain counts as one domain in all of them, and the underlying events are not comparable, so the share answers 'how many domains carry this marker' and not 'who leads this market'.
There is also no exclusivity between the rows. A company can serve a help centre, host a static documentation site and hold a verified workspace at the same time, and it would be counted in three places. That is a property of counting markers, and it is why I would use this table to size detectable footprints rather than to rank vendors.
An empty switching table, a churn number that means nothing, and a stack list that is really an account list
The migration section is empty on purpose, and not for lack of a result. A corridor from Zendesk returned 23 domains. I suppressed it because the two technologies do not do the same job: a support help centre is not a replacement for published API reference, and the signals are read off surfaces that cannot be lined up, one from the page and one from DNS that persists through any change the company made. A domain showing both has almost certainly switched nothing.
The churn figure needs the same treatment. 74 domains have dropped this detection since we began tracking in March 2026, 1.22% of the 6,068 here. That is not evidence of retention. Nobody deletes a DNS record when they cancel a subscription, so the number measures housekeeping, not loyalty. Any page built on account markers has this weakness, and the correct response is to stop quoting churn from it rather than to dress it up.
The co-occurrence table inherits the same bias, and it is legible once you know to look for it. Google Workspace at 42.68% and Atlassian at 34.72% are themselves verification-record detections, so what that block really lists is other products these companies verified a domain against. The rows below it are page-level and ordinary: Google Tag Manager 73.76%, Google Analytics 71.14%, Cloudflare 63.95%, Amazon Web Services 35.09%. What is absent is a vendor fingerprint. Nothing sits at 99% the way a hosted platform's own front end does, because the marker is DNS and the site next to it is whatever the company built. The one row I would flag as mildly informative is Tailwind CSS at 38.74% ahead of Bootstrap at 30.62%, which fits a base that is half software firms. Those percentages divide by the 6,247 domains our live crawl currently answers for, slightly wider than the 6,068 August rollup.
What to take from the page. This is a count of publicly verified Postman workspaces and published API docs, concentrated in small, young, technical companies across a wider set of countries than most enterprise profiles show, and it is honest about accounts rather than usage. Use it to size and segment a developer population. Do not use it to argue retention, market leadership or product engagement, because the marker underneath it cannot carry any of those. TechnologyChecker.io resolves the 6,068 detections against 5,144 identified organisations and refreshes them every month.
Frequently Asked Questions
Who uses Postman API Documentation?
Our live crawl finds it on 6,068 domains, and 5,144 of them, 84.8%, resolve to an identifiable organisation. Named users include Deloitte, Infosys, PwC, Marriott, Citigroup, Starbucks, UPS, Ford, AXA and SAP. Those names are the exception rather than the rule. The typical user is a small, young software team: 1,826 of the 5,116 companies that report a headcount, 35.69%, employ 11 to 50 people, Software Development is the most common industry at 1,276 of 5,063, 25.2%, and 82.03% of the 4,334 companies with a founding year were founded in 2000 or later.
How many customers does Postman API Documentation have?
We detect it on 6,068 active domains as of our August 2026 rollup, and 5,144 of those, 84.8%, resolve to a company record. Counts are domains, not accounts, seats or licences, and one organisation can hold several. The bigger caveat is what the marker means: most of these domains match on a DNS TXT record published once to verify a Postman workspace, so 6,068 is the number of domains that have ever been verified and still carry the record, which is not the same as the number of teams using the product today. A further 74 domains have dropped the detection since we began tracking in March 2026.
What is Postman API Documentation's market share?
It holds 3.49% of our Documentation & Knowledge Base category and ranks 4th in it, on 6,068 domains. Zendesk leads on 64.05% and 111,482 domains, with Foxit (5.0%), MediaWiki (3.5%), Docusaurus (3.16%) and Open Journal Systems (3.02%) around it. Two qualifications. The gap to third place is 29 domains, which is inside normal month-to-month movement, so read 3rd and 4th as level. And the rows are not measured the same way: the others are found in the page a visitor loads, while 96.6% of these detections are read from DNS. The share counts domains carrying a marker, not documentation traffic or spending.
What are the best alternatives to Postman API Documentation?
It depends which half of this row you are replacing. If you want a static documentation site you host yourself, Docusaurus (5,507 domains) and MediaWiki (6,097) are the two largest in the same category. If you want a hosted help centre for customer-facing support articles, Zendesk is the category leader by a wide margin at 111,482 domains and 64.05%, though that is a different job from publishing API reference. Foxit (8,700) and Open Journal Systems (5,253) round out the top five. Note that these are not mutually exclusive: a company can publish API docs from a Postman workspace and run a separate help centre, and both would be detected.
Which countries use Postman API Documentation the most?
The United States leads with 2,146 of the 5,006 companies we could place, 42.87%, then the United Kingdom on 399, 7.97%. Brazil is third on 232, 4.63%, ahead of Australia (196, 3.92%), Canada (193, 3.86%) and India (187, 3.74%). Germany (2.82%), France (2.56%), Netherlands (1.92%), Spain (1.5%), Singapore (1.12%), Mexico (1.08%), Switzerland (1.04%) and Italy (0.96%) complete the chart. The fourteen shown cover 79.96% of located companies, leaving 1,003, 20.04%, outside them, and 57.13% of the total outside the United States.
What size companies use Postman API Documentation?
Small ones, mostly. 1,826 of the 5,116 companies that report a headcount, 35.69%, employ 11 to 50 people, which is the largest band. Add the 1,018 companies at 1-10 and 2,844, 55.59%, employ fewer than 50; 3,872, 75.68%, employ fewer than 200. Only 585, 11.43%, employ more than 1,000, and 175, 3.42%, sit in the 10001+ band. Counted on domains instead of companies, 162 of the 6,068, 2.67%, belong to organisations with 8,000 or more employees. The enterprise names in the list further down are drawn from that 3.42%, because the list is ordered by audience size rather than by how typical a company is.
How old are companies that use Postman API Documentation?
Young. The 2010s are the largest bucket at 2,149 of the 4,334 companies with a founding year, 49.58%, and the 2020s add 756, 17.44%, so the two decades together are 67.03%. In total 3,555, 82.03%, were founded in 2000 or later, and only 779, 17.97%, predate it. Pre-1960 is 233 companies, 5.38%. The old names on the page are the tail of that distribution rather than its centre: Citigroup is recorded at 1812, Pfizer at 1848, Zurich at 1872, Chubb at 1882, Ford at 1903 and UPS at 1907.
What is the ideal customer profile for Postman API Documentation?
A software or IT company of fewer than fifty people, founded since 2000, that ships an API and needs somewhere to publish the reference for it. The numbers behind each clause: 48.79% of the 5,063 industry-tagged companies are software, IT services, internet or security firms; 55.59% of the 5,116 with a headcount employ fewer than 50; 82.03% of the 4,334 with a founding year date from 2000 or later. There is a second, thinner profile stacked on top of it, which is the large regulated firm running a partner API programme: financial services, insurance and banking are 15.94% of the industry-tagged base, and that is where Citigroup, AXA, Zurich and Fidelity Investments come from.
What does a Postman API Documentation detection actually mean?
One of four clauses matched. The main one is a DNS TXT record, postman-domain-verification, which a company publishes once to prove it controls a domain when it sets up a workspace. The other three read the page: a generator meta tag reading Postman Documenter, a PostmanRunObject JavaScript global, and a script served from a Postman host. The DNS clause dominates, and 8 of 8 domains we sampled carried a live record. So a detection means this domain has been verified against a Postman workspace, or is serving documentation the product generated. It does not tell you how many people use it, what the plan costs, or whether anyone opened the workspace this year.
Does this page count every company that uses Postman?
No, and it is worth being precise about the gap. Postman is used by developers on their own machines and inside private workspaces that leave no public trace, and none of that is visible to a crawler. What this page counts is companies that took one of two public actions: verified a domain against a workspace by publishing a DNS record, or shipped documentation the product generated on a site we crawl. Teams that use Postman purely internally will not appear here. Read 6,068 as a floor on public traces, not as a user count.
Why do only 3.4% of Postman API Documentation detections sit on a subdomain?
Because DNS resolves at the domain. A verification record lives on the apex, so a match on that clause can only ever be an apex or www result, and 96.6% of detections here are exactly that. The 3.4% that sit elsewhere are the three install clauses firing on documentation subdomains, which is the part of this row that genuinely reads published API docs. For contrast inside the same batch, the two purely DNS-matched profiles we published alongside this one are at 0% and 0.2% off the apex, on IBM Cloud and Docker respectively. That 3.4% is the fingerprint of the mixed rule.
Why do Google Workspace and Atlassian appear on so many Postman API Documentation domains?
Because they are found the same way this row is. Google Workspace appears on 42.68% of these domains and Atlassian on 34.72%, and both are detected primarily through domain verification records rather than anything on the page. A rule that finds companies which verify domains will find other products those companies verified domains against. Read that block as a list of accounts a company has set up, not as a description of what its website runs. The genuinely page-level rows are the ones underneath: Google Tag Manager at 73.76%, Cloudflare at 63.95% and Amazon Web Services at 35.09%.
Are companies leaving Postman API Documentation?
We cannot answer that from this signal, and the low churn number should not be read as if we could. 74 domains have dropped the detection since we began tracking in March 2026, 1.22% of the 6,068 counted here. A DNS TXT record does not expire and nobody removes it when they cancel a subscription, so a company could have stopped using the product years ago and still be counted. The 1.22% measures how rarely a DNS record gets cleaned up, which is a fact about DNS housekeeping rather than about retention. Treat every churn and loyalty reading on this page with that caveat attached.
Why is there no switching data on this page?
Not because the query came back empty. It returned a corridor of 23 domains from Zendesk, and we suppressed it deliberately. Two technologies only belong in a migration table if they do the same job for the same buyer, and a hosted help centre for customer support articles is not a replacement for published API reference. The measurement surfaces do not line up either: one signal is read from the page, the other from a DNS record that persists after any change. A domain carrying both has most likely changed nothing. We would rather publish an empty section than a corridor that reads like a trend and is not one.
Based on 5,144 company data
These insights include all TechnologyChecker.io detections of Postman API Documentation (free & paid plans).