*** title: About the API Catalog updated: 2026-03-01T00:00:00.000Z max-toc-depth: 2 ---------------- This feature is available on Postman Enterprise plans. For more information, see the [pricing page](https://www.postman.com/pricing/). The API Catalog is a central place to see all your APIs and services. You can connect your source code to the API Catalog, and it automatically shows you all your APIs in one place. You can also use the API Catalog to set rules for your APIs and check how well they're following those rules. The API Catalog works with Agent Mode, so you can ask questions about your APIs and get help with fixes when something is broken. To access the API Catalog, from Home icon **Home**, click **API Catalog**. ## What's inside The API Catalog consists of these main components: * Catalog List * Governance Groups * System Environments ### Catalog List The API Catalog shows all of your [discovered services](#discover-apis-and-services). You can filter and sort your API list in different ways. Use tags to mark which APIs you want to manage. The catalog shows who owns each API. You can also see how APIs are connected to each other and check health metrics. The API Catalog also shows you which APIs aren't properly managed with Postman Insights (if you have access). You can do the following: * Make views with your filters and tags. * Show different information at once. * Jump to the views you need. API Catalog list ### Governance Groups Governance groups help you make and enforce rules for your API specs like OpenAPI and AsyncAPI. You can have different rules for different types of APIs. For example, one set of rules for public APIs and another for internal APIs. This is how it works: * Developers using Postman can see these rules in the Postman app. * Postman CLI can pull these rules and enforce them in the CI pipeline. * You can configure the Postman CLI to block releases or trigger warnings. * Rules help score how well your APIs follow your own standards. ### System Environments System environments are your actual setups like production, staging, or beta. Setting these up helps Postman track your APIs correctly. When you run tests on multiple APIs, for example, system environments help group the results so you can see how each API performs. ## Discover APIs and services The API Catalog automatically shows all of your Git-connected Postman workspaces. To add something to the catalog, connect your Postman workspace to your source code. The API Catalog also shows APIs from API gateways and APIs discovered through Postman Insights. You can also set up a Kubernetes cluster custom resource as a watcher. You can also add APIs manually. To help get started quickly, the API Catalog provides the ability to discover services through multiple sources: * [Infrastructure (API Gateways)](/docs/api-catalog/connect/gateway/). * [Postman Insights](/docs/api-catalog/connect/insights/). * [Existing Postman Workspaces](/docs/api-catalog/connect/workspace/). * [Cluster Watcher](/docs/api-catalog/connect/watcher/). Using these workflows, you can find APIs that aren't managed in Postman yet and add them to the catalog. Postman sends a pull request to the API owner's repository. When the PR is accepted, a Git-connected project workspace is created, and the API shows up in the API Catalog. ## View the project Click any API to see its details. This shows all the data Postman knows about that API across development, test, and production. What you can do: * Open the Postman workspace or source code. * Check health metrics. * See how the API connects to other APIs. * Find endpoints that aren't properly managed (with Postman Insights). Use Ask Ai Chat icon Agent Mode to ask questions about your APIs and get help with fixes.