Postman Product Update: November 2025
This month, we’re highlighting features that close gaps across the API lifecycle. We’re sharing solutions that help you:
-
Keep specs and collections aligned from the start
-
Test private APIs in real-world conditions
-
Stay in flow with less duplication and context switching
Together, these improvements make it easier than ever to build, test, and manage APIs that teams (and AI agents) can rely on.
Let’s dive in.
Spec Hub updates keep APIs aligned and compliant
Over time, even small changes between specs and collections erode trust in your source of truth. As teams and specs continue to grow and evolve, bloated files, weak governance, and limited data residency support slow everything down.
Bidirectional sync keeps specs and collections in sync
Despite your best efforts, specs and collections never stay perfectly in sync. Updates happen on their own timelines, and small changes pile up fast. Teams lose time chasing the latest version and cleaning up messes caused by a lack of governance.
Bidirectional sync ensures that specs and collections stay in lockstep. When you update a collection, you can push those changes back to the spec. When the spec changes, update collections with one click. Ship faster with specs that everyone can trust.
Learn how to sync collections to specs (and vice versa!) ->
Governance reports enforce standards at scale
When you have hundreds of APIs across dozens of teams, it’s hard to spot inconsistencies early. Without visibility into spec quality or policy compliance, problems can reach production before anyone notices.
Governance reports in Spec Hub surface design and compliance issues early, so teams can address them before code is written. Reports help you identify which specs violate policies, track compliance across teams, and catch issues before they ship. Developers can open flagged specs directly from the report and make inline fixes. When developers and leaders share a single view of API health, it’s easier to enforce standards automatically and at scale.
Read the API governance report docs →
Multi-file specs simplify collaboration and organization
As API specifications grow in size and complexity, single-file formats become unmanageable. Long, monolithic OpenAPI files slow down iteration, cause merge conflicts, and make it difficult to enforce consistency across teams and services. The bigger your specs get, the harder they are to maintain.
Spec Hub’s multi-file spec support lets you break large OpenAPI files into modular components and organize them in a clear hierarchy. Cross-file references and intelligent autocomplete speed up editing (and prevent merge conflicts), while the outline view lets you navigate between files without losing your place. You can also separate endpoints, schemas, and examples for cleaner organization and easier collaboration across teams and services, allowing API design to scale cleanly as your organization grows.
Learn how to manage multi-file specifications ->
Spec Hub is now available for EU data residency
For developers in the EU, data residency requirements can be a barrier to using the tools you want. Your APIs need proper governance and design, but regulatory constraints rule out platforms that only operate in US data centers.
Now, you can store and manage your specs entirely within Postman’s EU data center. Your design artifacts and governance data stay in the EU region, so you can meet regional requirements without any extra overhead or compromise.
Learn more about EU data residency in Postman →
Test private APIs and validate releases in real-world conditions
Testing private APIs has always been messy. Firewalls, inconsistent environments, and limited visibility make it difficult to automate, govern, and scale testing with confidence.
Private API runners execute collections inside your network (Early Access)
Many APIs never touch the public internet, but you still need to test them. Private APIs sit behind firewalls, so external tools and monitors can’t access them reliably. Some teams rely on VPN tunnels, but those are prone to connection drops, require manual setup, and don’t scale well across environments, adding unnecessary complexity to testing.
With private API runners, you can install Postman CLI inside your own VPCs to run collections securely across dev, staging, and production environments and sync results back to Postman. This allows you to test your APIs in real-world conditions without exposing your infrastructure. Available for Enterprise customers. Request access here.
Learn more about configuring runners for internal APIs →
Runner management gives admins visibility and control (Early Access)
As teams start running monitors within their own infrastructure, the number of runners multiplies quickly. You might have several deployed, but no clear view of where they are, who owns them, or what to do when they fail. Without visibility or audit controls, security teams can’t confidently approve a wider rollout.
Runner management gives admins a centralized dashboard to monitor runner health, view audit logs, and manage workspace-level access. Platform and IT teams gain full visibility into every runner across the organization, making it easy to scale private monitoring and maintain compliance without introducing bottlenecks. Enterprise customers can request access here.
Learn more about managing runners for internal APIs →
On-demand monitors catch regressions at deploy time
Scheduled monitors run too late to catch deploy-time regressions. Without a validation gate at release time, these regressions can slip through. To avoid firefighting in production, QA and DevOps often compensate with duplicate tools and extra scripts.
Now, you can trigger monitors on demand. The monitors you rely on for health checks also serve as release gates, so you can catch issues before users do and prevent costly rollbacks.
Learn more about running tests with monitors →
Send monitor results to Slack or Teams
Even with monitors in place, teams may miss issues if they’re not proactively checking results in Postman or reading every email. Developers lose time learning about failures after the fact, instead of addressing them in real-time, which delays fixes and allows problems to escalate.
When creating or editing a monitor, you can now connect directly to Slack or Teams channels. Results are sent instantly to the spaces where teams already collaborate, so you can view monitor results in real time, respond to failures together, and maintain API reliability, all within your existing workflow.
Learn more about configuring a monitor ->
npm CLI distribution simplifies setup and adoption
Installing and updating the CLI through custom channels often requires IT intervention, which slows developers down and often adds unnecessary friction. You end up manually downloading releases from GitHub and dealing with inconsistent CLI versions across the team.
The Postman CLI is now available through npm, making installation and updates fast and familiar for developers. Teams can also integrate it directly into CI/CD pipelines to automate testing and quality checks with every release. Standardized distribution means fewer IT blockers, faster rollouts, and more consistent adoption of test automation capabilities across teams.
Install the Postman CLI with npm →
Stay in flow with less duplication and context switching
Developers lose momentum when they have to search across workspaces, rebuild requests that already exist, and manually log bugs. When teams waste time on repetitive tasks or fragmented workflows, productivity suffers.
Reusable requests prevent duplication across collections
Developers often duplicate the same requests across collections and test suites, manually updating endpoints, headers, and data each time. This usually happens when developers set up common steps like authentication, data seeding, or cleanup across multiple APIs or environments. It’s tedious, error-prone, and slows down automation.
With reusable requests via scripts, you can now call any request stored in a collection directly from another request’s script using the new pm.execution.runRequest function. Instead of duplicating or hardcoding endpoints, you can reference existing requests and run them inline. Your teams can reuse shared requests across collections, services, and even different workspaces to improve collaboration and keep tests and flows consistent.
Learn more about reusable requests with scripts ->
Collection status indicators show what’s ready to use
As workspaces grow, teams often rely on ad hoc naming conventions or informal tags like “draft” or “v1” to show where a collection stands. This approach works initially, but over time, it can lead to confusion, duplication, and slow onboarding as developers struggle to distinguish between current and deprecated collections.
Collection status indicators introduce structured lifecycle statuses for collections. You can apply preset status tags (in-development, ready-to-use, or deprecated) or create custom tags to match their workflow so it’s always clear what’s production-ready and what’s not. Statuses are visible in the collection overview, or you can search and filter for them through global search.
Create Jira issues directly from collection run results
When tests fail, logging bugs manually means switching tools, copying error details, and reconstructing context in Jira. This context switching wastes time and risks missing critical details about what actually broke.
You can now create Jira issues directly from collection run results. Failed test cases automatically populate Jira issues with failure details and timestamps, creating a tighter feedback loop between testing and triage. This lets teams resolve issues faster and keep work moving without switching tools.
Learn how to create a Jira issue from an API response →
Redesigned homepage surfaces what matters right now
With multiple workspaces and projects, developers lose time searching for the right APIs, requests, or recent activity. This constant context switching makes it harder to get back into the flow of work.
The redesigned homepage surfaces recent work, active workspaces, and tasks that need attention in one place. You can jump right back into what matters without hunting through tabs, which means less time spent searching and more time building.
Sign in to check out your new homepage →
Ship dependable APIs that humans and AI agents can trust
By connecting every stage of the API lifecycle, teams turn speed into confidence. Developers know their APIs are consistent and production-ready. Leaders know launches will scale smoothly.
These updates tighten gaps across the API lifecycle, reducing rework, increasing predictability, and helping teams stay aligned from design to delivery.
Explore them in Postman today and share your feedback in the Postman Community.
Want to see these features in action? Tune in to Between 2 Devs on LinkedIn Live to catch a demo of these new features.
Keep it 200,
The Postman Team
What do you think about this topic? Tell us in a comment below.