# New in Postman: Spec Hub Upgrades, API Governance & CLI Testing

Source: https://www.youtube.com/watch?v=eBpfudPN-XQ
Recap page: https://rapidrecap.app/video/eBpfudPN-XQ
Generated: 2025-11-11T02:40:05.785+00:00

---
## Quick Overview

Postman introduced significant November 2025 product updates including bidirectional sync for Spec Hub, governance reports, multi-file spec support, EU data residency, private API runners, on-demand monitors, npm CLI distribution, reusable requests, collection status indicators, Jira issue creation from collection runs, and a redesigned homepage.

**Key Points:**
- Spec Hub received major updates, including bidirectional sync that tightens the API workflow by allowing changes in collections to push back to the spec and vice-versa, eliminating drift and manual exports.
- New Governance Reports provide a complete view of spec quality across an organization, helping teams spot compliance or design issues before code is written.
- Support for multi-file specs allows breaking large OpenAPI files into smaller, manageable components with cross-file referencing and intelligent auto-complete.
- Private API Runners enable secure testing of internal APIs across Dev, Staging, and Production environments by installing the Postman CLI locally or within a VPC.
- On-demand monitors allow triggering collection runs directly from the CI/CD pipeline, serving as health checks or release gates.
- Reusable requests allow referencing existing requests in line within collection scripts, avoiding hardcoding endpoints and ensuring test consistency.
- Collection status indicators now clearly signal lifecycle stages (e.g., 'in-development', 'ready-to-use') on the collection overview, and Jira issues can be created directly from failed collection runs.

![Screenshot at 00:02: The title card announces "Postman Product Updates November 2025," highlighting key areas like Spec Hub, API Governance, and changes to the API workflow.](https://ss.rapidrecap.app/screens/eBpfudPN-XQ/00-00-02.png)

**Context:** This video presents the November 2025 product updates from Postman, delivered by Staff Developer Advocate Talia Kahan. The updates focus heavily on improving API specification management via Spec Hub, enhancing governance and compliance visibility through new reports, expanding testing capabilities with private API runners and on-demand monitors, and streamlining developer workflows with features like multi-file specs and reusable requests. The overall goal is to create tighter, more efficient workflows between API design and deployment.

## Detailed Analysis

The November 2025 Postman updates focus on enhancing API specification management, governance, and CI/CD integration. Spec Hub now features bidirectional sync, meaning edits in Postman collections update the spec, and vice-versa, preventing drift. Governance reports offer a consolidated view of spec quality, compliance, and design issues across an organization, visible on the homepage. Multi-file specs are now supported, allowing developers to break down large specifications into reusable components with cross-file referencing. For testing private environments, Private API Runners allow running collections securely inside VPCs or firewalls using the Postman CLI, with results syncing back to Postman. Furthermore, On-demand monitors enable triggering collection runs directly from CI/CD pipelines, acting as release gates or health checks. Workflow reuse is improved via reusable requests in test scripts, allowing referencing other requests without hardcoding endpoints. Collection status indicators provide clear lifecycle visibility ('in-development', 'ready-to-use') on the collection overview, and failed test runs can now automatically generate Jira issues, populating failure details automatically. Finally, the Postman homepage has been redesigned to offer a centralized view of recent activity and workspaces.

### Spec Hub & API Design

- Bidirectional sync implemented between specs and collections for seamless workflow updates
- Support added for multi-file specs allowing component reuse and better organization
- Cross-file referencing and intelligent auto-complete enhance editing large specs

### Governance & Visibility

- New Governance reports provide an overview of spec quality, compliance, and design issues organization-wide
- Collection status indicators allow setting lifecycle tags (e.g., 'ready-to-use', 'deprecated') visible on the collection overview

### Testing & CI/CD Integration

- Private API Runners enable secure testing of internal APIs within private networks (VPCs) using the Postman CLI
- On-demand monitors allow triggering collection runs directly from CI/CD pipelines for immediate validation

### Workflow Efficiency

- Reusable requests permit referencing other request scripts within a collection, eliminating hardcoding of endpoints
- Failed collection runs can now automatically create Jira issues, pre-populating failure details and timestamps

### User Interface Updates

- The homepage is redesigned to centralize recently visited workspaces, latest activity, and discovery resources for improved access

![Screenshot at 00:02: Title card announcing the November 2025 Product Updates, featuring icons for Spec Hub and Governance.](https://ss.rapidrecap.app/screens/eBpfudPN-XQ/00-00-02.png)
![Screenshot at 00:15: Demonstration of Spec Hub updates showing OpenAPI specification code, highlighting the ability to maintain specs and collections in sync.](https://ss.rapidrecap.app/screens/eBpfudPN-XQ/00-00-15.png)
![Screenshot at 00:26: Visual confirmation of the 'Bidirectional sync' feature being active between Spec Hub and collections.](https://ss.rapidrecap.app/screens/eBpfudPN-XQ/00-00-26.png)
![Screenshot at 00:46: The new Governance Reports overview screen displaying metrics like 'Open performance checks' and 'Non-compliant by weekly'.](https://ss.rapidrecap.app/screens/eBpfudPN-XQ/00-00-46.png)
![Screenshot at 00:54: Demonstration of 'Multi-file specs' showing a file explorer view with multiple JSON files within a spec structure.](https://ss.rapidrecap.app/screens/eBpfudPN-XQ/00-00-54.png)
![Screenshot at 01:25: The configuration screen for setting up a Private API Runner, showing options for selecting geographic regions \(e.g., EU, US West\).](https://ss.rapidrecap.app/screens/eBpfudPN-XQ/00-01-25.png)
![Screenshot at 01:54: Terminal session showing the successful installation of the Postman CLI via curl command, followed by triggering an on-demand monitor run.](https://ss.rapidrecap.app/screens/eBpfudPN-XQ/00-01-54.png)
![Screenshot at 02:48: Demonstration of Reusable Requests in a script, showing pm.sendRequest being called programmatically to reference another request.](https://ss.rapidrecap.app/screens/eBpfudPN-XQ/00-02-48.png)
![Screenshot at 02:49: Interface showing Collection Status Indicators where 'in-development' tag is applied, with options for 'ready-to-use' and 'deprecated'.](https://ss.rapidrecap.app/screens/eBpfudPN-XQ/00-02-49.png)
![Screenshot at 03:07: The 'Add to Jira Cloud' modal appearing after a collection run failure, showing fields being automatically populated with run details.](https://ss.rapidrecap.app/screens/eBpfudPN-XQ/00-03-07.png)