postman-app-support: The Official Bug Tracker and Feature Request Repository for Postman
Postman is an API platform for building and using APIs. Postman simplifies each step of the API lifecycle and streamlines collaboration so you can create better APIs—faster.
At a glance
- What is it?
- The postman-app-support GitHub repository is not the Postman application itself; it is a public issue tracker where users file bug reports, feature requests, and integration ideas for the Postman API platform. The application code is not open-source and is not hosted here.
- Who is it for?
- The postman-app-support repository is the correct destination for reporting Postman application bugs or requesting features, but it should not be confused with the Postman source code or a deployable artifact. Developers who need to communicate with the Postman team about application behavior should file an issue here following the CONTRIBUTING.md guidelines.
- Can I use it commercially?
- Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
- Is it still maintained?
- Yes. The repository last received commits 13 days ago.
- What is it written in?
- GitHub does not report a main language for this repository.
Answers come from the project's GitHub data, last synced on September 30, 2026, and from our analysis. They are not legal advice.
Editorial analysis
What This Repository Is and What Postman Does
Postman is an API platform used for building, testing, and using APIs. The README describes it as simplifying each step of the API lifecycle and making collaboration on API development faster. The postman-app-support repository on GitHub is the designated channel for community interaction with the Postman team on application issues.
This repository contains no application code. It exists as a structured issue tracker. Developers report bugs, suggest features, and propose integrations by opening issues here. The Postman application itself is a proprietary desktop and web application available at postman.com; the source code is not public in this repository.
The README states that Postman is used by more than 45 million developers and 500,000 organizations, including 98 percent of the Fortune 500. These figures come from Postman's own description in the README and are not independently verified here.
How to Use This Repository for Bug Reports
The README provides a clear workflow for bug reports. Before filing, search the issue tracker to check whether someone else has already reported the same issue. Finding an existing report is faster than waiting for a response to a new one, and the README calls this the fastest path to a solution.
When filing a new bug report, the README requests: detailed reproduction steps, the Postman version in use, the operating system version, and any additional files that help narrow down the issue. These include Postman collections, data dumps, browser console errors, and screenshots. The CONTRIBUTING.md file documents the full reporting guidelines.
The repository's release-notes/ directory contains release notes for Postman versions, which can help identify when a behavior changed between versions before filing a report.
For questions about billing or account-specific issues, the README explicitly redirects to the support page at postman.com/support rather than the GitHub issue tracker. This keeps billing disputes and account access problems out of the public issue tracker.
Repository Structure and What Is Actually in It
The repository contains four top-level entries: a .github/ directory for GitHub-specific templates and configuration, CONTRIBUTING.md with issue filing guidelines, README.md, and SECURITY.md for security vulnerability reporting, and a release-notes/ directory.
There are no source files, no build scripts, no tests, and no installable packages. The release-notes/ directory is the only content with substantive information beyond the README: it records changes across Postman versions and can help users understand whether a behavior change in a recent version is intentional or a regression.
The SECURITY.md file documents how to report security vulnerabilities, which is a separate path from the public issue tracker. Security issues typically should not be filed as public GitHub issues; SECURITY.md specifies the appropriate disclosure channel.
Where to Find Postman Documentation and Community Resources
The README points to several resources beyond the issue tracker for users who need to learn the application or troubleshoot problems. The primary documentation is at learning.postman.com, which covers features, installation, and usage in detail. The Postman blog at blog.postman.com publishes tutorials, development stories, and platform updates.
The Postman Community Forum at community.postman.com provides peer support from other Postman users. The README notes that lurking is possible without logging in, which lowers the barrier to finding answers. Signing in with a Postman account enables participation in discussions.
For updates on features and releases, the README identifies the X (formerly Twitter) account @getpostman as the best channel. Postman's company information and career listings are at postman.com/company/careers.
For the legacy Chrome extension version of Postman, issues and code contributions belong in the separate postmanlabs/postman-chrome-extension-legacy repository rather than this one.
Why Postman Attracts an Alternative Discussion
Postman's dominance as an API testing tool has prompted interest in alternatives, particularly after it ended its offline-capable free tier and moved more functionality to cloud sync and paid plans. The README does not discuss these product changes; they are not documented in this repository.
The search data associated with this repository shows people actively searching for alternatives, which reflects a real segment of the developer community that prefers self-hosted or fully offline tools. This is a legitimate concern: if a tool requires cloud account creation to function, teams in air-gapped environments or with strict data residency requirements may need to evaluate whether the current Postman terms meet their needs.
Insomnia, maintained by Kong, is the most commonly named alternative for API testing. It offers an open-source core and a self-hosted option. The difference in approach is that Insomnia prioritizes local-first operation and an open-source core, while Postman's current architecture is more deeply integrated with cloud services. The choice depends on whether the team needs advanced collaboration features that Postman's cloud provides, or local control that Insomnia's architecture supports.
License and Maintenance Status
The postman-app-support repository itself has no listed license, which is consistent with it being a support tracker rather than a software release. The Postman application is proprietary; its terms of service are documented on postman.com, not in this repository.
The last push to this repository was on 2026-09-18. The repository is actively maintained as a support channel, with new issues being processed. The release-notes/ directory receives updates when new Postman versions ship.
The hiring notice in the README points to postman.com/company/careers and mentions openings for engineers to work on the issues filed in this repository. This is a visible sign that the Postman team continues to invest in the product.
Editorial conclusion
The postman-app-support repository is the correct destination for reporting Postman application bugs or requesting features, but it should not be confused with the Postman source code or a deployable artifact. Developers who need to communicate with the Postman team about application behavior should file an issue here following the CONTRIBUTING.md guidelines. For billing and account questions, the README directs to the support page at postman.com/support rather than this issue tracker. Anyone evaluating Postman as an API platform should consult the learning.postman.com documentation rather than this repository.
Frequently asked questions
What is the Postman app for?
Postman is an API platform for building, testing, and using APIs. It covers the full API lifecycle from design through testing and deployment. The postman-app-support repository is specifically for filing bug reports and feature requests about the application.
Why stop using Postman?
The README does not document reasons to stop using Postman. Common reasons cited in the developer community relate to cloud account requirements and pricing changes, but those are not documented in this repository. Insomnia with its open-source core is an alternative for teams that need local-first operation.
Is the Postman app down?
Postman's status is not tracked in this repository. For current service status, check the Postman status page at postman.com or the @getpostman account on X, which the README identifies as the best channel for news on features and releases.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/postmanlabs-postman-app-support)