- Jan 20, 2026
- Parsed from source:Jan 20, 2026
- Detected by Releasebot:Jan 21, 2026
- Modified by Releasebot:Jan 22, 2026
Postman 11.81.1
Periodic activity summaries now arrive in Slack or Teams at scheduled times, not just in real time. Postman Monitors and scheduled runs gain monthly run scheduling, expanding automation options.
Improvements
Receive periodic activity summaries in Slack or Microsoft Teams
You can now opt to receive workspace activity summaries in Slack or Microsoft Teams at scheduled intervals besides the existing option of receiving them in real time. This is useful if your workspaces see a lot of activity or you want to provide high-level updates to a wider set of teammates.
To learn more see,
View Postman team activity in Slack
and
View Postman team activity in Microsoft Teams
.Monthly runs in Postman Monitors and scheduled runs
Original source Report a problem
Postman Monitors and scheduled runs now support monthly run schedule configuration. - Jan 13, 2026
- Parsed from source:Jan 13, 2026
- Detected by Releasebot:Jan 14, 2026
- Modified by Releasebot:Jan 15, 2026
Postman 11.80.1
Postman adds admin cert regeneration for SAML SSO and 30‑day expiry alerts, plus a unified Postman Flows experience that runs locally or in the cloud with seamless migration. These are user‑facing product updates for improved security and workflow flexibility.
Improvements
Regenerate SSO certificates
Postman now enables Admins to regenerate signing and encryption certificates in Postman’s SAML SSO settings. You can also now see a certificate expiry message 30 days before the expiration. To learn more, see Configure SSO for a team.
Introducing unified flows in Postman Flows
Postman Flows now has a single type of flow that can run locally and in the Postman Cloud. Postman Flows no longer separates flow modules that run locally and actions that run in the cloud. The new unified flow type has all the same functionality as modules and actions with more flexibility. Current modules and actions will migrate seamlessly to this new unified flow type, and will continue to run as they did before. To learn more, see Deployed flows overview.
Original source Report a problem - Jan 9, 2026
- Parsed from source:Jan 9, 2026
- Detected by Releasebot:Jan 13, 2026
Postman 11.79.5
What’s New
Introducing MCP Apps support for MCP requests
With Postman and MCP Apps, you can now experiment, test, and evaluate MCP servers with interactive UIs. MCP Apps is an extension of the Model Context Protocol (MCP) that standardizes how servers deliver interactive user interfaces.
For example, you can view data visualizations, such as interactive charts and graphs, directly in the response.
To learn more, see
Use your MCP request to interact with an MCP server
.
Original source Report a problem - Dec 19, 2025
- Parsed from source:Dec 19, 2025
- Detected by Releasebot:Dec 20, 2025
Postman 11.76.9
What’s New: Performance tests now show failed test assertions after runs with trend views and filtering to pinpoint issues under load. Improvements add more virtual users and automatic stop if resources are exceeded. Pilot phase; full rollout planned for early 2026.
What’s New
Introducing test assertions results in performance tests
After a performance test completes, you can now view requests with failed test assertions. This is useful for identifying why your API isn’t behaving as expected under load. View trends that occurred during the test to learn how test assertion failures changed in response to increased load on your API. Select a point on the trends graph to inspect the test assertions that failed at that point in time. You can also filter the results by an individual request that ran during the test to refine your results further.
This feature is currently in a limited pilot phase. A full rollout to all Postman plans is scheduled for early 2026.
To learn more, see
View failed test assertions for performance tests
.
Improvements
Increased virtual user limits in performance tests
You can now simulate more virtual users in performance tests, enabling larger load tests that reflect real-world traffic. This helps you model realistic scenarios and validate API stability under heavy use. Postman also alerts you when your system can't support the required load and automatically stops the test if it exceeds your machine’s resource limits.
This feature is currently in a limited pilot phase. A full rollout to all Postman plans is scheduled for early 2026.
To learn more, see
Virtual users and system resources
.
Original source Report a problem - Dec 16, 2025
- Parsed from source:Dec 16, 2025
- Detected by Releasebot:Dec 17, 2025
Postman 11.76.3
What’s New
Introducing the Console Log tab for manual collection runs
Collection runs now have a Console Log tab where you can view script-level console messages grouped by request. Badges identify each message as a log, info, warning, or error message.
Original source Report a problem - Dec 15, 2025
- Parsed from source:Dec 15, 2025
- Detected by Releasebot:Dec 17, 2025
Postman 11.76.0
Bug Fixes
Fixed an issue in Postman Flows that prevented the HTTP Request block from correctly showing resolved variables when users hover over the input port.
Original source Report a problem - Dec 12, 2025
- Parsed from source:Dec 12, 2025
- Detected by Releasebot:Dec 12, 2025
Postman 11.75.6
New in Spec Hub: Sync settings for OpenAPI 3.0 keep specs and collections aligned. Control how updates flow so parameters and request bodies sync with example values, helping maintain consistency as APIs evolve. Learn to configure from collection or specification.
What’s New
Introducing sync settings in Spec Hub
You can now customize how your OpenAPI 3.0 specifications in Spec Hub stay in sync with your collections. Sync settings give you more control over how updates flow between specifications and collections, so you can align behavior with the needs of your API project.
With sync settings, you can choose whether values in a collection, such as parameters and request bodies, sync with their corresponding example values in a specification. This makes it easier to maintain consistency as your APIs evolve.
Learn how to configure sync settings from a collection or specification.
Original source Report a problem - Dec 11, 2025
- Parsed from source:Dec 11, 2025
- Detected by Releasebot:Dec 18, 2025
Postman 11.75.4
What’s New
Introducing persistent environment variable changes in Postman Flows
HTTP Request blocks in Postman Flows modules now support persisting environment variable changes made with pre-request and post-request scripts. You can configure individual HTTP Request blocks to persist script-changed environment variable values when the block’s run completes. To learn more, see The HTTP Request block.
Original source Report a problem - Dec 9, 2025
- Parsed from source:Dec 9, 2025
- Detected by Releasebot:Dec 11, 2025
Postman 11.75.2
Improvements
Notebooks available to Postman teams
Postman Notebooks are now available to Postman teams. Team members can collaborate to create new notebooks, save and publish their work, edit existing notebooks, and revert to the last published version—all from the notebooks homepage. Notebooks can be accessed from the left sidebar on the Postman API Network page.
Original source Report a problem
To learn more, see
Create a notebook for the Postman API Network. - Dec 8, 2025
- Parsed from source:Dec 8, 2025
- Detected by Releasebot:Dec 9, 2025
Postman 11.75.1
What’s New
Filter collection and monitor run results by errors
Postman now has an Errors tab in collection runs, scheduled runs, and monitors where you can view a clear, structured list of all errors that occurred during a run. This enables you to surface all unique errors from the run and see errors grouped by request, making it easy to understand which request failed. You can also jump directly to the failing request to debug root causes faster.
Original source Report a problem