Postman release notes
Versions
Postman 12.27.5
September 10, 2026
Bug Fixes
Some critical bug fixes and enhancements were added in this release.
Postman 12.27.1
September 8, 2026
What’s New
Run cloud performance tests from static IPs
Available on Enterprise plans
You can now choose an egress routing strategy for cloud performance tests. Select Static IPs to send every request from a dedicated address you can allowlist in your firewall. This enables you to test targets behind a firewall or security group without exposing them to the public internet. Cloud performance tests and VU hour billing are also now available on Enterprise plans, matching Solo and Team plans.
To learn more, see Run a cloud performance test from static IPs.
Postman 12.26.3
September 2, 2026
Improvements
Run setup and teardown collections for performance tests in the Postman desktop app
You can now add setup and teardown collections to a performance test that runs from the Postman desktop app. The setup collection runs once before the test starts, so you can prepare what the test needs, such as creating an account or requesting an access token. The teardown collection runs once after the test ends, so you can clean up afterward, such as deleting the data the test created.
To learn more, see Run a performance test with setup and teardown collections.
Keep Flow blocks up to date with the latest snapshot
Flow blocks now make it easier to see when they’re using an older snapshot. If a Flow block isn’t using the latest snapshot, a warning appears with an Update to latest action.
You can also turn on Always use latest to automatically pin the Flow block to the newest reusable snapshot whenever one is published. Selecting an older snapshot turns off Always use latest and surfaces the update warning.
Postman 12.26.0
August 31, 2026
What’s New
Evaluate AI-generated output in Postman Flows
Postman Flows now supports AI evals for automatically grading AI-generated output against qualitative criteria. In the AI Agent block, you can enable built-in evals for friendliness, safety, non-toxicity, correctness, and relevance, or create your own custom evals.
You can also use pm.eval in the Evaluate block to define preset or custom evals with options such as thresholds, reference answers, context, and judge models. After your flow runs, you can review eval scores and reasons on the block, from the Evals output, and in the All Evals tab in the run log.
Postman 12.25.6
August 27, 2026
What’s New
Introducing Postman Datasets
Available on Solo, Team, and Enterprise plans
Postman Datasets are managed groups of structured data that live inside your workspace, designed to power realistic, repeatable, and scalable API testing. Create a dataset once and reuse it across collection runs, monitors, performance tests, mock servers, scripts, and Flows. It works in the Postman app, the Postman CLI, and CI environments.
Each dataset pulls from one or more sources and exposes views: saved SQL queries that select, filter, join, and transform fields for a specific test. Solo plans support CSV, JSON, and Excel file sources, including AI-assisted generation. Team and Enterprise plans can also connect to live databases, like MySQL and PostgreSQL. Enterprise plans additionally support custom JDBC drivers for many JDBC-compatible databases. Databases that aren’t publicly exposed are reachable over an SSH tunnel, and connection details can be stored as vault secrets in Postman Vault.
Agent Mode understands the datasets and views in your workspace. It uses your real field names when writing requests, tests, and scripts. You can describe the data you need so Agent Mode generates realistic test data for you.
To learn more, see Test APIs with datasets in Postman.
Run performance tests in the Postman Cloud
Available on Solo and Team plans
Run performance tests in the Postman Cloud to scale beyond the limits of a single machine, keep tests running after you close your computer, and persist detailed performance data for later review. Postman distributes the load across managed workers and streams metrics, errors, and test assertions live while the run is in progress, using the same collection and scripts you already test with. You can compare past runs and share results with your team.
You can also add setup and teardown collections to a cloud performance test, to prepare what the test needs before it starts and clean up once it ends.
To learn more, see Test API performance.
Pay-as-you-go for performance test VU hours
Available on Solo and Team plans
Cloud performance test runs now consume virtual user (VU) hours, based on the number of virtual users in a run and the test’s duration. Team Admins can view a detailed breakdown of VU hour usage by run, including the run name, source, collection, VU hours consumed, who created the run, and when it finished.
To learn more, see About resource usage.
Migrate your small team to Postman Organizations using a self-serve option
Available on Enterprise plans
You can now migrate your small team to organizations yourself directly from the Postman app.
To learn more, see Migrate your Enterprise team to an organization.
Postman 12.24.3
August 19, 2026
What’s New
Mocks are now available in Cloud View
Available on Solo, Team, and Enterprise plans
Mocks let you simulate APIs using custom JavaScript request handlers. In Cloud View, each mock receives a unique URL and is always available to handle requests.
You can also deploy a mock as a mock server, giving your team a cloud-hosted service they can send requests to at any time. By default, mock servers deployed from a mock are private and require workspace access or a valid Postman API key.
To learn more, see Build API mocks with JavaScript.
Postman Flows now available in the EU region
Available on Enterprise plans
Postman Flows is now available on the Postman EU Data Residency plan.
To learn more, see Postman EU Data Residency.
Postman 12.23.7
August 14, 2026
What’s New
Buy Postman from AWS Marketplace
You can now purchase Postman Team and Enterprise plans directly through the AWS Marketplace, consolidating Postman within your existing AWS billing.
There are two ways to get started:
- Subscribe from the AWS Marketplace listing and complete setup on a Postman-hosted page.
- In the Postman app, click Buy with AWS to purchase without leaving Postman.
Both flows support purchasing for your own team or on behalf of another team in your organization. All subscription changes are managed through the AWS Marketplace console.
Available for net-new Team and Enterprise plans.
To learn more, see Purchase AWS from AWS Marketplace.
Postman 12.23.0
August 10, 2026
What’s New
Introducing agent automations
Available as a beta feature
You can now create persistent cloud agents that run automatically based on triggers you define, including GitHub pull request and branch activity, and deliver their output to a destination you choose, such as Slack or pull request comments.
To learn more, see Use Agent Automations.
Use Datasets in Flows
Postman Flows now supports datasets in scenarios. You can attach a dataset view to a scenario and map its columns to the Flow’s inputs. The flow will run once for each row in the dataset, using that row’s data as input.
To learn more, see Assign input values with scenarios.
Postman 12.22.11
August 7, 2026
Bug Fixes
Fixed an issue in Postman Flows where references to requests inside collection folders failed to load in Cloud View after pushing a Git-backed workspace from Local Mode. Nested request references now work across Local and Cloud views without needing to be repaired manually.
Postman 12.22.3
August 5, 2026
Bug Fixes
Fixed an issue in Postman Flows where global variables mapped to vault secrets wouldn’t resolve when running flows in the cloud. Global and environment variables backed by vault secrets now resolve correctly during cloud runs.
Postman 12.22.2
August 4, 2026
What’s New
Edit your API specifications visually in Postman Spec Hub with the Visual editor
Edit your OpenAPI specifications visually without heavily relying on JSON or YAML. Postman’s Visual editor works across OpenAPI 3.1, 3.0, and 2.0 formats. You can switch to the Visual editor at any time from any specification you’re working on.
The Visual editor surfaces the right controls for each edit, such as plain text fields for names and summaries, Markdown editors for descriptions, code editors for responses, and schema builders for parameters and data types.
To learn more, see Edit an OpenAPI specification with the Visual editor.
GraphQL requests in Postman Flows
Postman Flows now supports GraphQL requests. With the new GraphQL Request block, you can run GraphQL queries and mutations in your flows and process the results using the same workflow as the HTTP Request block.
To learn more, see The GraphQL Request block.
API Request block in Postman Flows
The new API Request block enables you to add or create an HTTP, AI, or GraphQL request in your flow. The API Request block automatically transforms into the chosen request’s block type.
To learn more, see The API Request block.
Postman 12.21.9
July 31, 2026
What’s New
Introducing API security insights
The API Catalog now provides security insights so that you can monitor and manage security across your APIs. Connect a Wiz for security scanning, then drill into vulnerabilities, exposed secrets, and coverage gaps across your integrated services.
To learn more, see Monitor security findings across your API catalog.
Postman 12.21.2
July 29, 2026
Improvements
SDK Generator supports AsyncAPI specifications
You can now create TypeScript SDKs from AsyncAPI specifications for WebSocket APIs. You’re not required to make any adjustments to your configuration or CLI commands.
To learn more, see About Postman SDK Generator.
Postman 12.21.0
July 27, 2026
What’s New
Tag management
Available on Enterprise plans
You can now manage tags to control tag sprawl across your organization. You get flexible controls over who can create and manage tags, while allowing all of your teammates to organize elements with tags.
To learn more, see Manage tags.
Postman 12.20.1
July 21, 2026
What’s New
Code mocks are now available in Cloud View
Available as a beta feature
Code mocks let you simulate APIs using custom JavaScript request handlers and response logic. You can now create and run code mock servers in Cloud View, making it easier to develop, test, and share API simulations with your teammates.
Code mocks in Cloud View receive a unique URL and are always available to handle requests. If you’re on a paid plan, you can also deploy a local code mock as a mock server, turning it into a cloud-hosted service your team can send requests to at any time. By default, cloud code mock servers are private and can only be accessed by workspace members or callers that provide a valid Postman API key.
To learn more, see Simulate APIs with code mock servers.
Simulations are now available in Cloud View
Available as a beta feature on Solo, Team, and Enterprise plans
With Postman Simulator, you can now create and run simulations in Cloud View. Simulations let you apply conditions such as response delays, rate limits, and error responses across one or more code mocks, making it easier to test how applications behave under real-world conditions.
To learn more, see Simulate real-world conditions in Postman.
Track your interactions with the Postman Browser Tool
The Postman Browser Tool now records your interactions with a page as you browse. In the Interactions tab, you can review each event. This includes who drove it (Agent Mode or you), the action type, the Playwright locator used to identify the element, and the time since the previous interaction. You can also ask Agent Mode to generate Playwright tests or API requests and tests based on your recorded activity.
To learn more, see Capture traffic with the Postman Browser Tool.
Improvements
Keep code mocks in sync with collections and specifications
When you create a code mock from a collection or API specification, you can now choose to keep it synchronized with the source. Changes to the collection or specification are automatically reflected in the code mock.
To learn more, see Simulate APIs with code mock servers.
Inspect and debug state in code mocks
Code mocks now include improved state management and debugging tools. You can configure state sessions and inspect pm.state values to better understand and troubleshoot stateful behavior.
Use packages in code mocks
You can now use packages in your code mock implementations, making it easier to reuse code and extend mock server functionality. Code mock servers support packages from the Package Library and external registries.
More ways to access code mocks in simulations
Available as a beta feature on Solo, Team, and Enterprise plans
With Postman Simulator, you can now choose how requests access code mocks in a simulation. Use a URL path or request header to specify which mock server should handle a request.
These options make it easier to integrate simulations into different testing and development workflows.
To learn more, see Simulate real-world conditions in Postman.
Manage public code mock servers
Available on Team and Enterprise plans
Team Admins can now control whether code mock servers can be made public and require approval before a public code mock server is published.
To learn more, see Manage mock servers.
Postman 12.19.0
July 13, 2026
What’s New
Remove orphan requests sync setting now available in Spec Hub
Sync settings for linked specifications and collections now include the Remove orphan requests setting. When enabled, requests or endpoints missing from the source are cleared from the destination.
The setting works in both directions (specifications to collections, and collections to specifications), and is configurable per linked pair. The first sync after enabling shows a one-time confirmation prompt before any items are removed. Turn the setting off at any time to stop further deletions.
To learn more, see Spec Hub’s Sync settings.
Share local changes
You can now share your in-progress changes with your teammates before you push the changes to Postman Cloud. Your changes can include collections, environments, and API specifications.
To learn more, see Share local changes.
Postman 12.18.5
July 10, 2026
What's New
Run performance tests in the cloud
Available as a beta feature on Solo, Team, and Enterprise plans
You can now run performance tests in Postman's cloud infrastructure to simulate larger traffic loads.
To learn more, see Configure and run performance tests in Postman.
Postman 12.17.5
July 3, 2026
Bug fixes
Fixed an issue in Postman Flows where adding a new variable to a request's authentication wasn't reflected on the canvas until the app was restarted or the cache cleared. Variables now appear right away.
Postman 12.17.3
July 2, 2026
Bug fixes
Fixed an issue in Postman Flows where configuration values typed as Number arrived as text at runtime (for example, 8000 became "8000" ), which could break blocks expecting a real number.
Postman 12.17.2
July 1, 2026
Improvements
Postman Flows now saves changes made while offline
Postman Flows now saves your work locally when you're offline or off-VPN, so you don't lose progress. When you reconnect, you can either keep your offline changes or sync to the latest cloud version, and your offline edits are kept as a restorable snapshot.
Postman 12.16.3
June 25, 2026
What’s New
Use Postman Datasets in the cloud
Available as a beta feature on Solo, Team, and Enterprise plans
Datasets are now supported in the Postman cloud, making it easier to access, manage, and collaborate on datasets with your teammates. In Cloud View, you can create Postman cloud files as a data source, which is a CSV file stored in the Postman cloud. Push and pull changes between your local workspace and the Postman cloud to keep datasets in sync across environments. You can also share datasets with your teammates to collaborate on the same data and views.
To learn more, see Test APIs with datasets in Postman.
Introducing self-serve domain capture
You can now independently discover, claim, and consolidate users and data associated with your company domain without requiring support intervention.
To learn more, see Configure domain verification and account capture in Postman.
Introducing ability to add people to the team without approval
Available on Enterprise plans only
Organizations can now control how new members are added to the organization teams and whether they require approval.
To learn more, see Manage organization and team resources in Postman.
Postman 12.16.1
June 23, 2026
What’s New
Share secrets with your team using Postman Shared Vault
Available on Solo, Team, and Enterprise plans
You can now store and share sensitive data as vault secrets with Postman Shared Vault. Each workspace includes a shared vault that syncs secrets to the Postman cloud, enabling your team to securely access them across Postman apps and machines.
Vault secrets in a shared vault are end-to-end encrypted, with encryption keys managed by Postman. Because shared vault secrets are available in the Postman cloud, you can also use them with cloud-based features such as monitors and flows.
On Enterprise plans, Admins can control which workspaces have access to a shared vault, helping enforce security and governance across teams.
To learn more, see Store secrets in Postman Vault.
Proactively secure exposed secrets with Local Secret Protection
You can now use Local Secret Protection to detect and secure exposed secrets before they're synced to the Postman cloud or committed to a connected Git repository. When Secret Scanner detects sensitive data, like API keys and tokens, users are prompted to choose how to handle a secret. For example, a user could choose to move a detected secret to their Postman Local Vault.
On a Postman Enterprise plans, Team Admins can define workspace-level policies that control how detected secrets are handled across your organization.
To learn more, see Postman Secret Scanner.
Secure variable values for sensitive data
You can now mark variable values as secure to protect sensitive data, such as API keys and tokens. Secure variables use the same encryption process as Postman Vault, so sensitive values are encrypted instead of only being masked.
With secure variables, you can safely store sensitive values directly in global, environment, or collection variables without exposing them in your requests or collections.
To learn more, see Secure a variable value.
Use secure variables to reference vault secrets in requests
You can now more easily reference vault secrets by setting them as the value of a secure variable and using the variable in your request. This provides a consistent way to access secrets from both your Postman Local Vault and Postman Shared Vault. Secure variables are encrypted and designed for working with sensitive data.
Assign a vault secret to a global, environment, or collection variable, then reference it using the {{variable-name}} syntax. When the request runs, the vault secret's value is applied at runtime.
Postman still supports direct vault secret references using the {{vault:vault-secret-name}} syntax for secrets stored in your local vault only.
To learn more, see Use vault secrets in Postman.
Improvements
In Postman Flows, Schedule triggers can now pass the current time as an input on each run, with no custom code needed.
Postman 12.15.7
June 18, 2026
Bug Fixes
Fixed an issue causing the Success and Fail outputs of an HTTP Request block in a warning state to appear automatically, rather than only when the Output tab was clicked.
Postman 12.15.6
June 17, 2026
Bug Fixes
- Fixed an issue where the divider between the request and response panes in the HTTP request editor could not be dragged to resize.
Postman 12.15.5
June 17, 2026
What’s New
Analyze tests across runs in Application Inventory
The Application Inventory now includes a Tests tab that provides an aggregate view of test activity across runs. Analyze pass and failure trends across runs and branches, review run history for individual tests, and investigate the API activity associated with each test.
You can group results by UI test or API request, identify failures, and explore the API calls made during each run. Expand individual tests to see which branches they ran in and understand how test behavior changes over time.
To learn more, see Application Inventory overview.
Improvements
Improvements to Application Inventory filtering and run visibility
Application Inventory now includes a Runs metric that shows the number of test runs recorded against the selected system environment.
You can also filter and search across Dependencies, Tests, CI/CD Runs, and Dependency Graph views. Filter results by branch, status, and other criteria, or search for specific tests, endpoints, and dependencies to quickly focus on the information you need.
To learn more, see Application Inventory overview.
Postman 12.15.0
Jun 15, 2026
What’s New
Navigate web applications with the Postman Browser Tool
With the Postman Browser Tool, you can now browse and interact with web applications directly inside Postman. You can inspect page content, capture network traffic, and open requests in Postman. You can also use Agent Mode to automate browser workflows, generate tests, and create documentation from application behavior.
To learn more, see Capture traffic with the Postman Browser Tool.
Improved API Governance experience
Available on Enterprise plans only
API Governance now has a new experience in the API Catalog, built around complete Spectral rulesets instead of individual rules. The new experience introduces a dedicated governance workbench for authoring and managing rulesets, live validation while editing, reusable custom functions, and Governance Groups for applying rulesets across workspaces from a central interface.
Teams with existing governance data will continue to see the previous experience until they choose Move to New Experience in the API Catalog > Governance interface. This migration is one-time and can’t be undone.
To learn more, see Define and enforce API standards with governance groups in Postman.
Postman 12.14.5
June 12, 2026
Bug Fixes
Introducing API lifecycle reports
Fixed HTTP Request and AI Request blocks breaking in local workspaces. They could lose their connection to the saved request and fail to run when the app's stored IDs fell out of sync. Blocks now recover automatically.
Postman 12.14.3
June 10, 2026
What’s New
Introducing API lifecycle reports
Gain visibility into API activity across every stage of the API lifecycle. API lifecycle reports provide insights into development, testing, production, distribution, and API management, helping teams track adoption, analyze usage trends, and better understand how APIs are built, tested, deployed, and managed across the organization.
To learn more, see View reports about API activity across the API lifecycle.
Postman 12.14.2
June 9, 2026
Improvements
Duplicate specifications in Spec Hub
You can now duplicate a specification to create a copy you can edit without affecting the original. This is useful for creating a new version of your API while keeping the original as a reference, or for using an existing specification as a starting point for a new API.
To learn more, see Edit your API specification.
Bug fixes
Fixed a bug where cloning a flow failed on the web and desktop apps. Cloning now works as expected.
Postman 12.13.6
June 5, 2026
What’s New
Introducing Postman Sandbox for Enterprise testing
A Postman Sandbox is an isolated environment that includes standard Postman features so that they can be used for testing. It has its own members and resources. Use the sandbox to test and evaluate features before rolling them out to your full team.
To learn more, see Set up and manage a Postman Sandbox.
Improvements
Fork specifications in Spec Hub
You can now fork your Spec Hub specifications in Postman to create a copy and make changes without affecting the original. Forked specifications support pulling updates from the parent element using fast-forward merging, which replaces changes in the fork with changes from the parent.
For more information, see Collaborate with specifications in Postman.
Postman 12.13.5
June 4, 2026
Bug Fixes
- Fixed a bug in Postman Flows when switching between Output and Response blocks. Connections and fields are now handled correctly instead of dropping the connection or skipping the output field.
- Fixed a bug so the nested type selector in the Display block now shows the selected format instead of defaulting to JSON.
Postman 12.13.4
June 3, 2026
Bug fixes
Fixed an issue in Postman Flows where a flow using a shared module would break after it was pushed and then pulled. This would return an "Error occurred while executing the flow" message.
Postman 12.13.2
June 2, 2026
Improvements
Test results HTML report in Postman Flows
In Postman Flows you can now download your test results as an HTML report from the All Tests tab (in Run Logs and Analytics), alongside the existing formats.
New input added to Response blocks in Postman Flows
The Response block now has a Send input, letting a fail or conditional path trigger a response directly. This new Send input works both in the app and when running flows from the Postman CLI.
New Start block options in Postman Flows
When you create a new flow, the Start block gives you two new ways to jump right in:
-
API example: instantly loads a ready-to-run flow that shows a request, a test, and the results displayed on the canvas, so you can see Flows in action right away.
-
Create a Flow from collection: pick one of your collections and Flows automatically builds out the blocks for you, no manual setup needed.
Bug fixes
Fixed a bug so that scenarios now accept arrays and other non-object values in the Body field. Previously, saving would fail silently if the body wasn't a JSON object.
Postman 12.13.0
June 1, 2026
What’s new
Introducing Agent Mode on Cloud
The Postman Agent Mode on Cloud is an AI-powered agent that handles coding tasks so engineers can focus on reviewing and shipping rather than setting up and verifying. It can connect to your codebase, including repositories, workspaces, APIs, the frontend, and the backend, to perform complex, long-running workflows autonomously.
To learn more, see About Postman Agent Mode on Cloud.
Postman 12.12.7
May 30, 2026
Improvements
Aggregated test results in Postman Flows run logs
Run logs in Postman Flows now aggregate and display test results from all Request blocks in a single summary view for the entire flow.
Bug fixes
Resolved an issue in Postman Flows where the environment selector would not respond when trying to switch to a different environment.
Postman 12.12.3
May 27, 2026
Improvements
Move your Spec Hub specifications between workspaces
You can now move single and multi-file API specifications between workspaces, preserving all structure and metadata. Support covers all supported Spec Hub specification types: OpenAPI (2.0, 3.0, 3.1), AsyncAPI (2.0 and 3.0), GraphQL, protobuf (2 and 3), and Smithy 2.0.
Postman 12.12.1
May 25, 2026
Improvements
Rename component files in the Component Library
You can now rename component files in the Postman Component Library to keep your team's reusable components organized and easier to find.
To learn more, see Reuse specification components with the Component Library in Postman.
Bug Fixes
Fixed an issue that caused requests configured with authentication to fail to send.
Postman 12.11.3
May 20, 2026
What’s New
Introducing service account identities for automation and integrations
Available on Enterprise plans
System service accounts give your team a dedicated, non-human identity for automation, integrations, and system-to-system interactions. Instead of tying CI/CD pipelines or backend services to a person's credentials, you can create a service account that represents the system itself with its own access controls, credentials, and audit trail.
To learn more, see Manage service account identities for automation and integrations.
Improvements
Improved visibility for syntax errors and governance issues in Spec Hub
Spec Hub now has a unified Issues tab below the specification editor, making it easier to view and navigate validation results. Syntax errors and governance rule violations are organized into expandable sections, with details and direct links to their location in your specification.
To learn more, see Validate an API specification.
Bug Fixes
Fixed an issue that prevented the Postman desktop app from booting properly on Windows machines.
Postman 12.11.1
May 18, 2026
Improvements
AsyncAPI 3.0 support for Spec Hub
You can create, edit, and import your AsyncAPI 3.0 specifications in Postman’s Spec Hub.
To learn more, see Design API specifications in Postman.
Postman 12.10.5
May 14, 2026
What’s New
Test and debug webhooks in Postman
Available on Solo, Team, and Enterprise plans
-
Generate a public HTTPS URL to register with any webhook provider - Stripe, GitHub, Slack, Linear, and others.
-
Inspect full request payloads and headers in real time, with shared visibility for your whole team.
-
Forward incoming requests to a localhost server or any URL.
-
Replay any captured request with one click.
-
Configure dynamic responses to handle provider handshakes such as Slack URL verification.
To learn more, see Webhooks in Postman.
Postman 12.10.3
May 12, 2026
Improvements
Archive unused components in the Postman Component Library
You can now archive components in the Postman Component Library. Existing references to archived components remain functional, but the component can't be edited and new versions can't be published while it's archived. If you need it again, an API Governance Manager can restore the component at any time.
To learn more, see Reuse specification components with the Component Library in Postman.
Postman 12.10.2
May 12, 2026
What’s New
Automate SDK updates with Postman and GitHub
Available on Enterprise plans
Postman can auto-generate client SDKs from a collection or spec and publish them to a linked GitHub repo. You can configure package distribution via package managers like npm for TypeScript SDKs. Changes to the collection or specification, like adding or removing requests, trigger a new SDK build and open a pull request with updated code. If you’re on a Team plan, you can still connect your SDK with GitHub and update it manually, but automated updates require an Enterprise plan.
To learn more, see Automate SDK updates with Postman and GitHub.
Postman 12.10.1
May 11, 2026
Improvements
Sync collections with your API specifications in Local View
You can now sync changes between Postman Collections and API specifications in Local View on the Postman desktop app. This is supported for OpenAPI 2.0, 3.0, and 3.1 specifications in your local Git repository.
To learn more, see Generate collections from your API specification.
Postman 12.9.7
May 8, 2026
What's New
Validate API dependencies from your Playwright tests
Available on Solo, Team, and Enterprise plans
You can now use the Application Inventory to track the applications you build, the external APIs they depend on, and the test coverage validating those dependencies. The Application Inventory integrates with your existing Playwright test suite to automatically capture API interactions and validate them against your Postman Collections. This catches issues UI assertions alone miss, like contract drift, silent backend errors, and missing or incorrect API calls.
To learn more, see Application Inventory overview.
Postman 12.9.4
May 6, 2026
Improvements
Support for Smithy 2.0 in Spec Hub
You can now create and edit Smithy 2.0 specifications directly in Spec Hub.
For more information, see Design and build your APIs in Postman.
Postman 12.8.4
April 30, 2026
Improvements
Expanded region support for Postman Monitors
Postman Monitors now support additional regions, giving you more flexibility to run checks closer to your users and infrastructure. New locations include Asia Pacific (Hong Kong, Seoul), Europe (Ireland, Paris), India (Mumbai), Japan (Osaka, Tokyo), and US East (Ohio), with more regions available.
To learn more, see Run monitors in different regions.
Postman 12.8.3
April 29, 2026
Bug Fixes
Restored the ability to click on a run log entry in the Postman Flows canvas to navigate directly to the corresponding block. This navigation had stopped working in a previous release.
Postman 12.8.0
April 27, 2026
Improvements
Tag changelog entries with versions
You can now add version tags to your changelog to label and organize updates to your API specification. Tag the latest set of changes to group them under a specific version, view those changes in read-only mode, and share a direct link with your team.
To learn more, see Add a version tag to the changelog.
Bug Fixes
Fixed a regression introduced in app v12.7.6 where Evaluate, If, and Condition blocks stopped working in the Postman desktop and web app. Cloud-based flow runs were not affected.
Fixed an issue where Evaluate blocks would not execute with a ‘Result is undefined’ error message.
Fixed an issue in the HTTP Request block where input variables were being stripped when a path parameter used colon syntax (:resourceId) with a {{resourceId}} value, causing broken variable injection in flows.
Postman 12.7.5
April 23, 2026
What’s New
Introducing new SDK Generator languages: Kotlin, Ruby, and Rust
Available on Team and Enterprise plans
The Postman SDK Generator now supports three additional languages: Kotlin, Ruby, and Rust. Combined with existing support for TypeScript, Java, Python, C#, Go, PHP, and CLIs, you can now generate SDKs for your APIs in ten languages.
To learn more, see Generate SDKs in Postman.
Share API health with published monitor reports
Available on Solo, Team, and Enterprise plans
You can now publish read-only monitor reports that provide visibility into your API's uptime, performance, and recent run results. Anyone with the link can view the report in a browser without needing a Postman account or workspace access. This makes it easy to communicate API reliability to external stakeholders.
Published monitor reports show the last 30 monitor runs. Reports include the overall health status, success rate, and request-level details such as response times, status codes, and the number of test assertion failures. Monitor Editors can publish reports for monitors they have access to. On Enterprise plans, a Team Admin must approve requests to publish. Each monitor can have one published report at a time.
To learn more, see Share API health using monitor reports in Postman.
Bug Fixes
Fixed an issue where HTTP requests using form data would lose their Content-Type header when run in Flows local mode, causing different behavior from cloud mode.
When using Postman Flows with Native Git (Local) mode, the "Allow scripts to update environment variables" option is now available, closing a gap with Cloud mode where this setting already existed.
Postman 12.7.4
April 22, 2026
What’s New
Agent Mode report
You can now track Agent Mode usage, user engagement, and AI credit consumption using the new Agent Mode report. To view the report, go to your homepage, click Reports in the left sidebar, and select Agent Mode.
To learn more, see Agent Mode report.
Postman 12.7.2
April 21, 2026
What’s New
Automate collection runs using the Postman CLI from Local View
When running a collection in Local View, you can now select the Automate runs via CLI option to quickly get started with the Postman CLI. This displays the Postman CLI installation command and a postman collection run command with the path to your collection in your local Git repository.
To learn more, see Run a collection locally with the Postman CLI.
Postman 12.7.1
April 20, 2026
What’s New
Connect Flows deployed as MCP Servers
The AI Agent Block now supports MCP servers as tools, meaning you can connect any Flow deployed as an MCP server and let the agent call it during execution. This brings composable, reusable logic into your AI workflows: instead of rebuilding capabilities inside a single Flow, you can expose them as MCP servers and let the agent decide when and how to use them.
To learn more, see The AI Agent block.
MCP Trigger Block
Postman Flows now supports MCP (Model Context Protocol) as a trigger type. Create and deploy Flows as MCP servers to use them as tools in other AI applications and Flows. Generate tool definitions with AI or define custom schemas manually.
To learn more, see Create a deployable flow with an MCP block.
Postman 12.5.5
April 9, 2026
What’s New
Visualize test assertion failures under load
Postman now supports the Tests vs VU view in performance test results, giving you a clear view of how your test assertions behave as load increases. This view includes a heatmap that highlights failure rates across virtual user levels, helping you quickly identify when and where your business logic starts to break under load.
To learn more, see View test assertions by virtual user load in performance tests.
Improvements
File watcher support in Postman Flows
When working in Native Git mode in Postman Flows, local file changes now automatically sync to the Postman app. This works whether you're editing in your IDE, terminal, or file explorer.
Folder support in Postman Flows
Create and organize Flows in folders locally. Folder structures automatically mirror in the app, and push/pull operations maintain your organization without dependency conflicts or rename issues.
Postman 12.5.2
April 7, 2026
What’s New
Generate CLIs from your Postman Collection or API specification
Available on Team and Enterprise plans
You can now generate a fully-functioning command-line interface (CLI) application based on your Postman collections or OpenAPI specifications. The CLI has been enhanced with two main end-users in mind: Agents (LLMs) and humans.
To learn more, see Generate CLI from your collection or specification.
Postman 12.5.0
April 6, 2026
Bug fixes
Fixed an issue where environment variables in the Request block would resolve based on the global environment instead of the environment selected in the block itself, ensuring variables display correctly.
Postman 12.4.5
April 3, 2026
What’s New
View deployed flows in the Services tab
You can now view deployed flows in the Services tab for a centralized view of all running flows alongside other services.
Postman 12.4.4
April 2, 2026
What’s New
Access Flow operations through the command palette
You can now access Flow operations Run, Share, Deploy, and Create through the command palette(⌘+Shift+O or Ctrl+Shift+O), so you can quickly trigger actions without navigating through menus.
Postman 12.4.3
April 1, 2026
What’s New
Introducing new SDK Generator languages: PHP, Go, and C#
Available on Team and Enterprise plans
The Postman SDK Generator now supports three additional languages: PHP, Go, and C#. Combined with existing support for TypeScript, Java, and Python, you can now generate SDKs for your APIs in six languages.
To learn more, see Generate SDKs in Postman.
Postman 12.4.0
March 30, 2026
Bug fixes
Fixed an issue where files with the .flow extension were not being recognized during a push to the cloud, preventing syncing of flow files.
Postman 12.3.7
March 27, 2026
What’s New
Command palette
The command palette enables you to navigate Postman's features and UI elements using keystrokes and natural language, making it easier to work on your APIs without pointing and clicking.
To open the command palette, press ⌘+Shift+P or Ctrl+Shift+P, or enter “>” in the search bar. The search bar expands to suggest features as you type a navigation command.
To learn more, see Navigating Postman.
Improvements
Two-way synchronization support for OpenAPI 3.1 collections and Spec Hub
Postman now supports a two-way synchronization between OpenAPI 3.1 specifications and collections. Whether you generate a collection from an OpenAPI 3.1 specification or an OpenAPI 3.1 specification from a collection, you can now make changes to either, then sync your changes to the other.
Postman 12.3.6
March 27, 2026
Improvements
Usage metrics in Postman reports now update every hour instead of monthly
Improved data freshness: You will see data for the current month up to the last hour. Current usage metrics for the last month have been replaced with data from the last 30 days with updates every hour.
Enhanced visualization: Bar charts have been replaced with Sankey charts to easily identify which API partners are successful or dropping off.
Postman 12.3.5
March 26, 2026
Improvements
Improved migration for Git-linked APIs to Spec Hub
You can now specify a directory path when migrating Git-linked APIs from the API Builder to Spec Hub. This makes it easier to migrate from repositories that have multiple APIs organized by folder, giving you more control over which API is migrated.
To learn more, see Migrate your API specifications from the API Builder to Spec Hub.
Postman 12.3.0
March 23, 2026
Improvements
Changelogs for Spec Hub
Track every update to your specifications with Spec Hub changelogs, a chronological history of changes that shows when edits were made, who made them, and exactly where in the specification they occurred.
To learn more, see View specification changes with the changelog.
Postman 12.1.1
March 10, 2026
What’s New
Introducing Fern
You can now publish your Postman Collection as a full documentation site powered by Fern. Configure your branding, colors, and logo, then click Publish. Fern automatically generates your API reference and deploys it to a live site backed by a GitHub repository. From there, you can add guides, tutorials, and overview pages, customize your branding and domain, and enable AI-powered features like intelligent search.
To learn more, see Document your APIs with Fern.
Postman 12.0.1
March 1, 2026
Postman v12 introduces a new platform designed for the agentic era, with features that help teams move APIs from development to production for internal, external, and agentic use. It integrates with Git-based workflows and offers new capabilities: Git-connected Workspaces, an API Catalog that manages APIs and services organization-wide, an updated Private API Network for internal API distribution, and much more.
Read on for more about what's new in this version of Postman.
What’s New
Native Git
The new Postman app is Git-native from the ground up. This means you can work in Postman on the same branch you’re writing code on, alongside your IDE, and the Git-native architecture enables Postman to work in offline conditions too.
You can now open the local instance of your remote Git repository where your API is implemented. The collections, specifications, and environments you work on in Postman are saved as a folder inside the source code folder. Work on your iterations locally until the API reaches a stable, deployable state, then commit your local changes to Postman Cloud.
A new file editor enables you to edit and create files directly in the Git folder connected to your workspace. Git workflows are native throughout: there's a code editor, a terminal, and a new modifications UI for pushing and pulling changes without leaving Postman.
To learn more, see About Native Git.
Introducing the Collection 3.0 format
The new Collection 3.0 format enables teams to organize HTTP, GraphQL, gRPC, MCP, MQTT, WebSockets, and AI requests in the same collection. Instead of JSON blobs, collections are broken into constituent YAML files that are easy to diff, easy for humans to review, and easy for AI agents to read and write.
You can now use Collection Runner with gRPC and GraphQL to build a single, consistent testing and automation workflow locally, in the CLI, or in a pipeline.
Multi-protocol collections - including GraphQL, gRPC, WebSocket, MQTT, MCP, and SOAP - can now segment authentication by route for per-protocol or per-route authentication. Enterprise teams can now run scripts at a collection level per protocol.
To learn more, see Test your API using Collection Runner.
Introducing local mock servers
You can now create a mock server that simulates a real API server in your local Git repository, where you're making API changes. This enables you to quickly set up your service locally by mocking the APIs it depends on.
You can create a local mock server from a template to define logic yourself or use Agent Mode to quickly get started. You can also use the Postman CLI to validate your collection’s tests against a mock server or start a mock server in your CI/CD pipeline. Once your local mock server is running, you can send requests to it just like a real API.
To learn more, see Simulate your API locally using a Git-backed mock server.
Introducing monitoring internal APIs with runners
Available on Enterprise plans
With Private API Monitoring, you can now monitor your organization’s internal APIs behind a firewall or deployed in a restricted network, like a virtual private cloud (VPC). This means you can monitor internal APIs without exposing your endpoints to the public internet.
Use the Postman CLI to start the runner in your own network where it polls Postman for monitor runs, runs the collection and its tests in your network, and sends the results back to the Postman cloud. Any of your teammates can choose the runner when they create a monitor, making it easy for anyone on your team to test internal APIs.
As an Admin, you can create and manage your team’s runners from Runner settings, which is located in your Organization or Team settings. Here you can view more details about runners, like their health status, last ping date, and more. You can also view each active instance of a runner to help you scale your team’s runners.
To learn more, see Monitor internal APIs with runners.
Introducing API Catalog
Available on Enterprise plans
The API Catalog is a central place to see all your APIs and services. It is a live operational layer for API portfolio management that functions as a system of record that stays current because it is directly connected to where your APIs are built, tested, and run. You can connect your source code to the API Catalog, and it will automatically show you all your APIs in one place. You can also use the API Catalog to set rules for your APIs and check how well they're following those rules. The API Catalog works with Agent Mode, so you can ask questions about your APIs and get help with fixes when something is broken.
To learn more, see About Postman API Catalog.
A new, more organized UI
Built for developers and AI agents, the new Postman UI delivers a clean, information-dense, efficient workbench with every major capability - including collections, environments, specs, and flows - one click away.
The centerpiece of the new UI is a unified workbench. Collections, environments, specs, flows, and mock servers can now live together and be organized however makes sense for the work at hand. Developers can work across everything relevant to their development process at once instead of switching between separate contexts. Agent Mode ties this together by operating across multiple elements simultaneously.
Introducing the new Private API Network
Available on Enterprise plans
Your new Private API Network is a curated subset of your organization's internal workspaces, organized by team. It's a place where you can discover the internal APIs most relevant to your work.
Search and Postman Agent Mode are optimized for your new Private API Network. And a new badge helps you identify trusted sources from your organization, no matter where you are in Postman.
To learn more, see Discover your organization's internal APIs with your Private API Network.
Introducing SDK Generation
Available on Team and Enterprise plans
The SDK Generation Service enables Postman users to automatically generate client SDKs from their Postman Collections or OpenAPI specifications. The service transforms API definitions into production-ready SDK code in multiple programming languages (TypeScript, Python, Java, and more), which users can download and integrate into their applications.
To learn more, see About Postman SDK Generator.
Introducing Native Git for Flows
Build and manage Postman Flows directly on your local filesystem with Git-native workflows. Create, edit, and delete flows locally while automatically switching between Cloud View and Local View.
To learn more, see Manage flows with Native Git.
Introducing support for MCP Servers in Postman Flows
The AI Agent block v2 can now connect to external MCP servers via a URL with bearer token authentication in Postman Flows. Build AI agents by connecting to MCP Servers and using their available tools.
To learn more, see AI Agent block.
Introducing support for environment variables and vault secrets in Postman Flows
You can now reference environment variables and vault secrets in Configurations, Scenarios, and Deploy settings. Values are automatically pulled from your selected environment or vault for both manual and cloud execution.
To learn more, see Configure values for flows.
Improvements
Agent Mode
Agent Mode acts as both a coach and hands-on collaborator in your workflow. You can interact conversationally, run end-to-end tasks, and directly modify code to fix errors or generate server stubs and client code. It works across Postman and connected repositories to create and update collections, tests, and mocks according to organizational standards—all without switching tools. Built-in capabilities like AI Test Generation automatically add contract, load, unit, integration, and end-to-end tests to improve coverage and prevent regressions. AI Debugging identifies root causes of failed runs in Collection Runner, Monitors, and Performance tests and suggests fixes directly in the results, significantly reducing troubleshooting time.
Postman is also introducing Agent Mode Enterprise features, designed to meet the security, governance, and access control requirements of large organizations. New capabilities for Enterprise plans include fine-grained user access control that lets administrators grant Agent Mode access to all users, specific individuals, or selected groups and teams, enabling pilot programs, role-based access, and phased rollouts. Enhanced security guardrails automatically protect sensitive data with secret redaction (using Postman Secret Scanner to prevent API keys and credentials from reaching LLMs) and PII redaction (using AWS PII Guardrails to mask personally identifiable information).
Additionally, MCP governance controls help manage Model Context Protocol server integrations with enterprise-grade oversight, allowing administrators to allowlist specific MCP servers or block all MCP servers to maintain security and compliance.
To learn more, see Postman Agent Mode Enterprise features.
Support for generating OpenAPI 2.0 specifications from collections
From a Postman Collection, you can now generate OpenAPI 2.0 specifications in Spec Hub. You can now also sync changes between collections and OpenAPI 2.0 specifications.
To learn more, see Generate an API specification from your collection.
Deprecated Features
Postman API Builder
The Postman API Builder is no longer supported. API specification management moves to Spec Hub.
Learn how to migrate your API specifications from the API Builder to Spec Hub.
Deprecated integrations
Git and CI/CD integrations are no longer supported.
Git and CI/CD workflows move to Native Git and the Postman CLI. API Gateway integrations move to the API Catalog.
Export performance tests in PDF or HTML format
Exporting a performance test report in PDF or HTML format is deprecated. Postman recommends exporting performance test reports in JSON format.
To learn more, see View metrics for performance tests.
Postbot
Postbot is no longer available in Postman v12. You can use Agent Mode instead. Agent Mode brings an AI-native experience to Postman, enabling automation across a wide range of API use-cases.
To learn more, see Agent Mode.
The #1 platform for API testing, development, and collaboration
Trusted by 40M+ developers to test, build, and scale APIs faster.
