Postman Release Notes
Last updated: Mar 2, 2026
Postman Products
All Postman Release Notes (201)
- March 2026
- No date parsed from source.
- First seen by Releasebot:Mar 2, 2026
Postman CLI v1.31.3
Postman CLI adds private API monitoring with enterprise runners behind firewalls, enabling in-network tests that report to the cloud. It also supports performance tests, mock servers, SDK generation from collections or OpenAPI, local flows for Enterprise, and multi‑protocol runs (gRPC, GraphQL) for CI/CD.
What’s New
Support for Private API Monitoring with runners (Available on Enterprise plans)
With Private API Monitoring, the Postman CLI now supports monitoring your organization’s internal APIs behind a firewall or deployed in a restricted network. This means you can monitor internal APIs without exposing your endpoints to the public internet.
Use the postman runner start command to start a runner with your runner’s ID and key. Once running, the runner polls Postman for upcoming monitor runs. The collection and its tests run in your network and the results are sent back to the Postman cloud.
To learn more, see Monitor internal APIs with runners.
Support for running performance tests
The Postman CLI now supports configuring and running performance tests against collections in your team. Performance tests enable you to simulate real-world traffic to your APIs and automatically surface performance issues before changes reach production.
Use the postman performance run command to integrate performance tests into your CI/CD pipeline and ensure your APIs stay fast and reliable with every release. The Postman CLI sends the results to the Postman cloud to help you debug performance test results.
To learn more, see Run a performance test using the Postman CLI.
Support for mock servers
The Postman CLI now supports using a mock server to run against your collection’s tests. This helps you validate your tests against the mocked responses of external APIs used in your service, both locally and in CI environments. With the Postman CLI, you can integrate a mock server into your CI/CD pipeline with the --mocks option when you run a collection with postman collection run.
You can also use the postman mock run command in your CI/CD pipeline to start a mock server as a dependency for your application or test suite. The mock server runs on the specified port until you stop it. This is useful for simulating an API server for your service or external tests.
To learn more, see Postman CLI command options.
Support for generating SDKs from collections and API specifications
The Postman CLI now supports generating client SDKs directly from your Postman collections or API specifications (such as OpenAPI). Generate production-ready SDKs in TypeScript, Python, and Java, making it easy to provide consumers of your API with idiomatic client libraries.
Use the postman sdk generate command with a collection ID, specification ID, local file, or publicly accessible URL as input. You can generate SDKs for one language at a time, multiple languages, or all supported languages at once using the --all flag. Generated SDKs are written to a configurable output directory (default ./sdks) with a subdirectory per language.
postman sdk generate <collection-or-spec-id> --language typescript python --output-dir ./sdksTo customize SDK generation, use the postman sdk init command to create a .postman/config.json configuration file where you can set the SDK name, version, authentication behavior, retry policies, and per-language options.
Additional SDK management commands are available:
- postman sdk list — List previous SDK builds for a collection or specification.
- postman sdk fetch — Download SDKs from a previous build by its build ID.
- postman sdk connect — Connect a collection to a GitHub repository for automated SDK pull requests. Once connected, use the --pr flag with postman sdk generate to automatically create pull requests with updated SDKs.
Support for running flows locally with the Postman CLI (Available on Enterprise plans)
You can use the postman flows run command to run local flows without exposing private APIs and sensitive data to the Postman cloud. The postman flows run command has options to set input values, show run log information, and use values from a scenario.
To learn more, see Postman CLI command options.
Improvements
Support for multi-protocol collection runs
The postman collection run command now supports gRPC and GraphQL collection runs.
To learn more, see Postman CLI command options.
Original source Report a problem - Mar 1, 2026
- Date parsed from source:Mar 1, 2026
- First seen by Releasebot:Mar 2, 2026
Postman 12.0.1
Postman v12 launches a Git-native, all‑in‑one platform with Collection 3.0, local mocks, API Catalog, Private API Network, SDK generation, and Agent Mode enhancements designed for enterprise teams to ship APIs faster across environments.
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 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.
Original source Report a problem
To learn more, see Agent Mode. All of your release notes in one feed
Join Releasebot and get updates from Postman and hundreds of other software products.
- Feb 17, 2026
- Date parsed from source:Feb 17, 2026
- First seen by Releasebot:Feb 19, 2026
Postman 11.85.1
What’s New
Introducing AI request blocks for Postman Notebooks
With Postman Notebooks and AI request blocks, you can add a block to your notebook and create an interactive experience with an AI model. For example, your notebook can take the response from an API call and analyze it with an AI model of your choice.
To learn more, see Add AI request blocks to your notebook.
Original source Report a problem - Feb 16, 2026
- Date parsed from source:Feb 16, 2026
- First seen by Releasebot:Feb 19, 2026
Postman 11.85.0
What’s New
Introducing new Reports experience
Available on Enterprise plans
Postman Reports now assist your decision-making with two groups of metrics: workspace analytics and team and organization analytics. You can use reports to understand how your team is using Postman, identify your most active users and spot trends in API usage. The Reports now also include:
- New charts focused on API collaboration
- New Partner Analytics page that helps you track how successful external partners are at onboarding your APIs
- New Postman API endpoints to programmatically fetch this data
- Feb 9, 2026
- Date parsed from source:Feb 9, 2026
- First seen by Releasebot:Feb 19, 2026
Postman 11.84.0
What’s New
Introducing workspace archiving
Available on Enterprise plans
You can now archive inactive workspaces. Archiving a workspace removes it from your active workspace list and places it in the Archived workspaces section of your workspaces dashboard. You can restore archived workspaces at any time.
To learn more, see Manage Postman workspaces.
Original source Report a problem - Feb 5, 2026
- Date parsed from source:Feb 5, 2026
- First seen by Releasebot:Feb 19, 2026
Postman 11.83.5
Improvements
New Slack Connector block in Postman Flows
You can now use the new Slack Connector block in Postman Flows, enabling you to automate tasks like sending messages and managing channels as part of your workflows.
Original source Report a problem - February 2026
- No date parsed from source.
- First seen by Releasebot:Feb 4, 2026
Postman CLI v1.29.5
Improvements
Various internal enhancements were added in this release.
Original source Report a problem - Feb 3, 2026
- Date parsed from source:Feb 3, 2026
- First seen by Releasebot:Feb 19, 2026
Postman 11.83.2
Improvements
Support for gRPC and GraphQL in Spec Hub
Original source Report a problem
Postman’s Spec Hub now supports designing, building, and importing protobuf 2, protobuf 3, and GraphQL specifications. This improvement also includes support for multi-file protobuf 2 and 3 specifications.
For more information, see Design and build your APIs in Postman. - Feb 2, 2026
- Date parsed from source:Feb 2, 2026
- First seen by Releasebot:Feb 19, 2026
Postman 11.83.0
Improvements
Comments in Spec Hub specifications
Postman’s Spec Hub now supports comments, enabling teams to collaborate directly on API specifications. Use top-level comments to discuss, review changes, and share feedback within the specification.
Original source Report a problem - Jan 30, 2026
- Date parsed from source:Jan 30, 2026
- First seen by Releasebot:Feb 19, 2026
Postman 11.82.5
New reusable components in Spec Hub let Enterprise teams create and publish a component library for OpenAPI specs, standardizing schemas and responses across projects. Vault secrets export/import adds flexible Local Vault backups with admin controls.
What’s New
Introducing reusable components in Spec Hub
Available on Enterprise plans
With the Postman Component Library, you can now create reusable components for your team's OpenAPI specifications in Spec Hub. You can create reusable components for schemas, responses, and more. This enables you to maintain and standardize commonly used components in a central location, without redefining components in each specification. Publish a new version of a component so your teammates can reuse it in their specifications.
To learn more, see Reuse specification components with the Component Library.
Export and import vault secrets
You can now export vault secrets from your Postman Local Vault to preserve them in an encrypted or unencrypted JSON file for later. This is useful for preserving your vault secrets when you sign out of Postman, switch between Postman apps, or switch between machines. Import your vault secrets back in to your Postman Local Vault to continue sending requests with your vault secrets.
Admins on a Professional or Enterprise plan can manage whether teammates can export vault secrets. Admins can also specify if teammates can export vault secrets in encrypted format, unencrypted format, or both.
To learn more, see Export and import vault secrets.
Original source Report a problem