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

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.

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.