Improvements

Run setup and teardown collections for performance tests in the Postman desktop app

You can now add setup and teardown collections to a performance test that runs from the Postman desktop app. The setup collection runs once before the test starts, so you can prepare what the test needs, such as creating an account or requesting an access token. The teardown collection runs once after the test ends, so you can clean up afterward, such as deleting the data the test created.

To learn more, see

Run a performance test with setup and teardown collections
.

Keep Flow blocks up to date with the latest snapshot

Flow blocks now make it easier to see when they’re using an older snapshot. If a
Flow
block isn’t using the latest snapshot, a warning appears with an
Update to latest
action.

You can also turn on
Always use latest
to automatically pin the
Flow
block to the newest reusable snapshot whenever one is published. Selecting an older snapshot turns off
Always use latest
and surfaces the update warning.

What’s New

Evaluate AI-generated output in Postman Flows

Postman Flows now supports AI evals for automatically grading AI-generated output against qualitative criteria. In the
AI Agent
block, you can enable built-in evals for friendliness, safety, non-toxicity, correctness, and relevance, or create your own custom evals.

You can also use
pm.eval
in the
Evaluate
block to define preset or custom evals with options such as thresholds, reference answers, context, and judge models. After your flow runs, you can review eval scores and reasons on the block, from the
Evals
output, and in the
All Evals
tab in the run log.

What’s New

Introducing Postman Datasets

Available on Solo, Team, and Enterprise plans

Postman Datasets are managed groups of structured data that live inside your workspace, designed to power realistic, repeatable, and scalable API testing. Create a dataset once and reuse it across collection runs, monitors, performance tests, mock servers, scripts, and Flows. It works in the Postman app, the Postman CLI, and CI environments.

Each dataset pulls from one or more sources and exposes views: saved SQL queries that select, filter, join, and transform fields for a specific test. Solo plans support CSV, JSON, and Excel file sources, including AI-assisted generation. Team and Enterprise plans can also connect to live databases, like MySQL and PostgreSQL. Enterprise plans additionally support custom JDBC drivers for many JDBC-compatible databases. Databases that aren’t publicly exposed are reachable over an SSH tunnel, and connection details can be stored as vault secrets in Postman Vault.

Agent Mode understands the datasets and views in your workspace. It uses your real field names when writing requests, tests, and scripts. You can describe the data you need so Agent Mode generates realistic test data for you.

To learn more, see

Test APIs with datasets in Postman
.

Run performance tests in the Postman Cloud

Available on Solo and Team plans

Run performance tests in the Postman Cloud to scale beyond the limits of a single machine, keep tests running after you close your computer, and persist detailed performance data for later review. Postman distributes the load across managed workers and streams metrics, errors, and test assertions live while the run is in progress, using the same collection and scripts you already test with. You can compare past runs and share results with your team.

You can also add setup and teardown collections to a cloud performance test, to prepare what the test needs before it starts and clean up once it ends.

To learn more, see

Test API performance
.

Pay-as-you-go for performance test VU hours

Available on Solo and Team plans

Cloud performance test runs now consume virtual user (VU) hours, based on the number of virtual users in a run and the test’s duration. Team Admins can view a detailed breakdown of VU hour usage by run, including the run name, source, collection, VU hours consumed, who created the run, and when it finished.

To learn more, see

About resource usage
.

Migrate your small team to Postman Organizations using a self-serve option

Available on Enterprise plans

You can now migrate your small team to organizations yourself directly from the Postman app.

To learn more, see

Migrate your Enterprise team to an organization
.

What’s New

Mocks are now available in Cloud View

Available on Solo, Team, and Enterprise plans

Mocks let you simulate APIs using custom JavaScript request handlers. In Cloud View, each mock receives a unique URL and is always available to handle requests.

You can also deploy a mock as a mock server, giving your team a cloud-hosted service they can send requests to at any time. By default, mock servers deployed from a mock are private and require workspace access or a valid Postman API key.

To learn more, see

Build API mocks with JavaScript

.

Postman Flows now available in the EU region

Available on Enterprise plans

Postman Flows is now available on the Postman EU Data Residency plan.

To learn more, see

Postman EU Data Residency

.

What’s New

Buy Postman from AWS Marketplace

You can now purchase Postman Team and Enterprise plans directly through the AWS Marketplace, consolidating Postman within your existing AWS billing.

There are two ways to get started:

• Subscribe from the AWS Marketplace listing and complete setup on a Postman-hosted page.
• In the Postman app, click Buy with AWS to purchase without leaving Postman.

Both flows support purchasing for your own team or on behalf of another team in your organization. All subscription changes are managed through the AWS Marketplace console.

Available for net-new Team and Enterprise plans.

To learn more, see

Purchase AWS from AWS Marketplace.

What’s New

Introducing agent automations

Available as a beta feature

You can now create persistent cloud agents that run automatically based on triggers you define, including GitHub pull request and branch activity, and deliver their output to a destination you choose, such as Slack or pull request comments.

To learn more, see Use Agent Automations .

Use Datasets in Flows

Postman Flows now supports datasets in scenarios. You can attach a dataset view to a scenario and map its columns to the Flow’s inputs. The flow will run once for each row in the dataset, using that row’s data as input.

To learn more, see Assign input values with scenarios .

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
.

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

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.