Postman API Health Scorecards Now Live in the API Catalog
Quick Reads
- Postman’s API Catalog now includes Postman API health scorecards for Enterprise plan users
- Each scorecard pulls data from test runs, spec linting, and connected API gateways
- The catalog layout is redesigned around the API development lifecycle
- Teams can access scorecard data via the Postman API v1.39 endpoints programmatically
- African engineering teams scaling API governance stand to benefit from this centralised visibility
Postman just shipped Service Health Scorecards inside its API Catalog for Enterprise teams. The update gives platform teams one unified quality signal per service, and closes a real gap. Before this, identifying a degrading API meant clicking into each one individually.
Each scorecard draws from three sources: collection run test pass rates, spec compliance results from linting, and production metrics from connected API gateways. Therefore, platform teams managing dozens of services across multiple squads can now get a quick read without deep-diving into every API.
Moreover, the more data a team connects, the richer the scorecard becomes. Teams already running spec linting in CI pipelines will see compliance results feed directly into the scorecard. Production metrics from a connected API gateway behave the same way. Even teams using only scheduled monitors still receive health data. However, spec compliance and gateway signals only appear once those sources are connected.
Beyond scorecards, Postman also redesigned the catalog layout. It now organises around the API development lifecycle rather than just metadata and spec details. As a result, development activity, test results, and production signals appear together in one view. The intent is clear: follow an API’s health from build time through production, without switching tools.
For API governance teams specifically, this changes how they prioritise. Currently, spotting APIs that need attention typically requires a weekly manual review across monitor dashboards, test reports, and spec compliance results. That process is slow, and things slip through. With Postman API health scorecards aggregated at catalog level, a quick scan now surfaces low-scoring services automatically.
This pairs well with the Postman API v1.39 endpoints for the API Catalog. Teams can pull catalog data programmatically and feed it into governance dashboards or internal reporting tools.
For Nigerian and African engineering teams scaling API-first products, the practical value is significant. Many organisations here manage sprawling API estates across multiple product lines. A single health view at catalog level reduces review overhead and keeps distributed teams aligned, consequently, without requiring expensive tooling overhauls.
The feature is available exclusively on the Postman Enterprise plan. To get started, consult the API Catalog overview in Postman Docs and the gateway connection guide.
