Postman release notes

Postman 12.4.4

April 2, 2026

Bug Fixes

Some critical bug fixes and enhancements were added in this release.

Postman 12.4.3

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