What’s New

AsyncAPI SDK generation from the CLI

You can now generate SDKs from AsyncAPI specifications directly using the Postman CLI. You can only generate SDKs in languages that support AsyncAPI, helping you avoid errors when selecting an output language.

List your workspaces from the CLI

You can now use the postman workspace list command to list all the Postman workspaces you have access to, showing each workspace’s ID, visibility type, and name. Use --filter to narrow results by name. You can add --json to return the results in JSON format.

Improvements

More reliable flow execution when collections are reorganized

The Postman CLI now runs flows correctly even when the requests they reference have been moved or renamed in a collection. Previously these runs failed with an error that the collection items could not be found, which blocked CLI automation and CI/CD workflows. This brings CLI flow runs in line with how the same flows already run in the Postman app. If a flow still reports this error, re-save it in the Postman app to update it to the current format.

Bug Fixes

Fixed an issue where streamed response bodies were dropped during flow capture preloading, which could cause incomplete data to be recorded during flow execution.

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
.

Improvements

Control how workspace elements sync to the cloud

The postman workspace push​ command now supports a --push-strategy option that gives you more control over how your local Git repository syncs to the Postman cloud. Use the --push-strategy force-sync option to mirror your local Git repository. This creates and updates elements in the Postman cloud, and also deletes elements from the cloud that have no local counterpart. When running in a CI/CD pipeline, you can pair force-sync with --yes to skip the interactive confirmation.

Scoped traffic filters for application test runs

Available on Solo, Team, and Enterprise plans

The filters configuration in postman.config.cjs now supports scoped array entries. Each entry in the array can target specific tests by file path or Playwright tag. This enables you to exclude different URLs, methods, and headers depending on which tests are running. Filters with no target or tags field apply to all tests.

The filters configuration still supports a single object that's applied to all tests.

Deprecated Features

Path options deprecated for workspace commands

The --collections-dir and --environments-dir options are deprecated for the postman workspace prepare and postman workspace push commands.

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.

What’s New

Raw run data streaming for v3 collections

Available as a beta feature on Enterprise plans

You can now use the postman collection run command with the --output option to stream raw run data to YAML files on disk as each request finishes.

Manage webhook requests with the Postman CLI

The postman webhook requests command is now available to help you manage requests received by a webhook. You can list requests, inspect request details, and replay requests for testing and debugging.

Report CLI events to Postman

The postman collection run and postman spec lint commands now support a --report-events option that uploads run results and governance rule violations to Postman, where you can view them in the API Catalog.

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.

Improvements

Richer Git metadata for application test runs

The postman app test command now automatically captures Git metadata for each test run, including commit information, tags, parent commits, git describe output, Git notes, and whether the working tree has uncommitted changes. This information is included with the run's analytics without requiring any extra configuration.

The captured metadata makes it easier to associate test runs with specific commits and releases. For example, you can identify release builds by tagged commits or use your own tag naming convention to determine which runs correspond to a release. In CI environments, the command also captures Git metadata from supported CI providers when available.