Postman Release Notes

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.

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.

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.

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. …

What’s New

Read requests and folders in a collection without exporting it

The postman collection request get and postman collection folder get commands print a single request or folder from a collection, either locally or from the cloud. You can inspect an item before changing it instead of reading collection files by hand.

View a single specification file

The postman spec file get command prints the contents of one file from a specification without reading the whole specification. This helps you review contract details from the terminal.

Create a secret in your team’s Shared Vault

The postman secret create command adds a secret to your team’s Postman Shared Vault. This streamlines secure credential management as part of your automation and CI workflows.

Create and manage examples under a request

The postman collection example command family lets you add, update, get, list, and remove examples (saved responses) under a request. It works on local v3 collections or cloud collections.

Improvements

Schema-valid values when generating collections from OpenAPI …

What’s New

Run a subset of requests in a monitor

You can configure a monitor to run a subset of its collection’s requests instead of the full collection. Pass -i, --item <id> (repeatable) to postman monitor create or postman monitor update to list the requests or folders to include, in the order you want them to run. On postman monitor update, --clear-items resets the selection so the monitor runs every request again.

Import a collection from a curl command or HAR file

The new postman collection import <src> command creates a Postman Collection from a curl command or a HAR file.

Improvements

View a scenario’s endpoints for a mock

The postman mock get command now lists the endpoints for every scenario associated with a mock, not only the default one. This enables you to discover and use non-default scenario endpoints without leaving the CLI.

SSL options and a cookie jar for a request

The postman request command now accepts SSL configuration and cookie jar options. This gives you more control over request behavior when working with secured endpoints or session-based APIs.

Lint warning for request file names

The postman collection lint command warns when a .yaml or .yml request file in a collection folder doesn’t use the required .request.yaml suffix. This helps you catch misnamed request files before you run the collection.

JSON output for more workspace commands …

What’s New

Publish collection documentation to the cloud

The postman collection publish command publishes a cloud collection’s public documentation, making it visible to anyone, or requests Community Manager approval when your workspace requires it. Configure the publish with --environment, --title, --description, and --note, and add --json for machine-readable output.

Improvements

See full request and response details while a mock runs

The postman mock run command now streams the same detailed request and response log as postman mock log, with secrets redacted. Pass --output ndjson for a machine-readable event stream instead.

Every worksheet in a spreadsheet becomes its own dataset source

The postman dataset source add command now adds every worksheet in a spreadsheet (xlsx, xls, ods) as its own queryable datasource, named source_<worksheet>.

Keep a request’s URL and query parameters in sync

The postman collection request update command now updates a request’s stored query parameters to match whenever you pass the --url option with a new query string. The postman collection lint command now flags a request whose query parameters and URL don’t match.

Installers add Postman CLI awareness for coding agents …

What’s New

Delete a specification

The postman spec delete command removes a specification by its cloud ID or local file path. Pass -y or --yes to skip the confirmation prompt, and --api-key to authenticate when you delete by cloud ID. Deleting a specification can’t be undone.

Remove a workspace dependency

The postman dependency remove command removes a workspace dependency and deletes its local files. Identify the dependency by its cloud ID, display name, or on-disk name from the postman dependency list command. Removing a collection also removes the environments pinned to it, unless another collection pins them too.

Improvements

Protect an existing collection from being overwritten

The postman spec generate collection command no longer overwrites an existing local collection, so it can’t erase the test scripts you added to it. To regenerate and replace that collection on purpose, pass --force.

Use datasets in a mock’s request handlers

The postman mock run command accepts a --dataset option that loads one or more local .dataset.yaml files, or directories of them. The mock’s request handlers can then read them with pm.datasets(<id>). Pass --dataset more than once to load several.

Bug Fixes

• Fixed the postman request command so a response with a non-2xx or non-3xx status code exits with code 1. …

What’s New

Delete a workspace from the CLI

The postman workspace delete <workspaceId> command permanently deletes a workspace and everything in it.

Disconnect a workspace from Git

The postman workspace disconnect-git [workspaceId] command removes the Git integration from a workspace without leaving the CLI. It disconnects the workspace in Postman and clears the connection in .postman/resources.yaml. No local files are deleted. With no ID, it disconnects the workspace this folder’s connected to. Pass --yes to skip the confirmation prompt in CI.

Two-way sync between specifications and collections

You can now keep a specification and its generated collection linked and regenerate either side on demand. The postman spec generate collection <spec> command creates a collection from a specification and records the link. The postman spec sync collection <spec> command regenerates the collection from its linked specification. In the other direction, postman collection generate spec <collection> creates an OpenAPI specification from a collection, and postman collection sync spec <collection> regenerates the specification from its linked collection. Both directions work in local and cloud modes.

Improvements

Mock run history is recorded …