What’s new in Postman: API health scorecards in the Postman API Catalog

The Postman API Catalog now includes Service Health Scorecards to close that gap. Each service in your catalog gets an aggregated health signal built from data across the API lifecycle, and the catalog layout has been updated to reflect that lifecycle structure. This is available on the Postman Enterprise plan.

Here’s what changed.

What Service Health Scorecards show

The scorecard gives you a unified quality signal per service built from three sources: test pass rates from collection runs, spec compliance from linting checks, and production metrics from connected API gateways.

If a service is degrading, you see it at catalog level rather than per-API. That’s the core change. Platform teams and API governance leads managing many services across multiple squads no longer need to click into each API to know whether it’s healthy. The catalog does the aggregation for you.

The more data you’ve connected, the more complete the picture. Teams that already run spec linting in their CI pipelines will see those compliance results feed directly into the scorecard. Production metrics from a connected API gateway work the same way. If you’re only running scheduled monitors today, you’ll still get health data; it just won’t include spec compliance or gateway signals until you connect those sources.

The lifecycle-centric catalog view

Beyond the scorecard itself, the catalog layout has changed. It’s now organized around the API development lifecycle rather than just metadata and specification details.

Development activity, test results, and production signals now sit together in one view. The intent is that you can follow an API’s health from the time it’s being built through to how it’s running in production, all without switching tools.

I’ve seen platform teams use the API Catalog as their “source of truth” for what APIs exist and who owns them. Adding health data to that same view means fewer context switches during service reviews and service level agreement conversations. Instead of pulling up a separate monitor or asking a team for their last test run report, the catalog tells you.

Getting started

If you’re on the Postman Enterprise plan and your team already uses the API Catalog, the scorecard data will appear in the service view when you open a service.

To get the most complete picture:

1. Sign in to Postman and select API Catalog in the left sidebar.
2. Open a service and check the health scorecard section.
3. If data is sparse, check whether your collections are running on a schedule. The Postman Monitor setup docs cover how to set those up.
4. Connect your API gateway to the catalog if you want production metrics included. The gateway connection docs have the setup steps.

If you’re not yet using the API Catalog, the catalog overview in Postman Docs is the right starting point. It covers how to register APIs, connect workspaces, and pull in the signals the scorecard depends on.

What this means for API governance

For teams running API governance programs, the scorecard changes how you prioritize. Right now, identifying which APIs need attention usually means a weekly review cycle where someone manually checks monitor dashboards, test reports, and spec compliance results. That’s slow, and things fall through the gaps between reviews.

With health data aggregated at catalog level, a quick scan of your API inventory tells you where to focus. Services with low scores surface automatically rather than waiting to be caught in a scheduled review.

This pairs well with the Postman API v1.39 endpoints for the API Catalog, which you can use to pull catalog data programmatically. If you want to build a governance dashboard or integrate catalog health data into an internal reporting tool, those API endpoints are where to start.

Things to watch for

Scorecard accuracy depends on what you’ve connected. A service with no associated collection runs and no gateway connection will show an incomplete scorecard. Start by making sure your most critical services have at least monitors configured so there’s test data to pull from.

The lifecycle view is new. If your team has existing workflows built around the catalog’s previous layout, it’s worth taking a few minutes to orient to where things now live before your next service review.

Enterprise only. If your team is on the Postman Team plan and this feature matters to you, it’s worth flagging to whoever manages your Postman account. The pricing page has the plan comparison.

Resources

• About the API Catalog – Postman Docs
• Connect your API gateway to the API Catalog
• Set up a Postman Monitor
• CI spec linting with Postman API Catalog
• New in the Postman API v1.39: API Catalog and Spec Hub endpoints
• Postman pricing and plans