Postman Release Notes

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.

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.

What’s New

Control automatic pull request creation

The postman sdk connect command now supports the --auto-update-pull-requests option to control whether pull requests are created automatically when the source changes or a new version of the SDK Generator is released. When this option is set to false, pull requests are created only when SDK regeneration is triggered manually.

If you don't specify the option, the default behavior depends on your Postman plan. It defaults to true for Enterprise plans and false for Team plans.

Prevent duplicate elements when pushing to a workspace

The postman workspace push command now helps prevent accidental duplicate Postman elements. If an element with the same name already exists in the Postman cloud, you're prompted to update the existing element, keep both, or skip it.

Improvements

Automatic npm publishing for generated SDKs

The postman sdk connect command no longer needs the --enable-publishing option. Generated SDKs now include the npm publishing workflow by default. To publish packages automatically, configure the required GitHub Actions secrets in the connected repository.

Improved logging for workspace commands

The postman workspace prepare and postman workspace push commands now support the --verbose option to display detailed logs, including API requests and responses, internal actions, and additional troubleshooting information. Error messages have also been improved to make issues easier to understand and resolve.

Bug Fixes

Fixed an issue where the postman collection run command could incorrectly skip requests containing valid path variables or query parameters.

Fixed an issue where pm.environment.name and pm.environment.id returned undefined in scripts.

What’s New

Create and query datasets with the Postman CLI

Available as a beta feature

The Postman CLI now supports the postman dataset command for creating datasets, managing data sources, running SQL queries, and running saved views. Datasets enable you to work with reusable data from files and databases in local development and automation workflows, including CI/CD pipelines.

You can also use the --iteration-data-dataset , --iteration-data-view , and --dataset options with the postman collection run command to run collections using dataset-backed iteration data or make datasets available to collection scripts.

To learn more, see Dataset commands.

Improvements

Postman Flows cloud runs for non-Enterprise users

Postman Flows cloud runs are now available to non-Enterprise users. Users can run a deployed flow via postman flows run without needing a private runner, with improved error feedback.

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.

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.

Improvements

Automatic SDK version selection

The --sdk-version option is now optional in the postman sdk generate command. If omitted, Postman automatically determines the SDK version based on changes to the API specification, collection, or SDK Generator, and defaults to 1.0.0 for the first generation.

Bug Fixes

Fixed an issue where postman flows run could return a Missing required inputs error when a flow contained unconnected input ports.

Fixed an issue where using pm.environment in scripts would return undefined values incorrectly.