Definition
API Catalog is a Setup feature that provides a centralized directory of all available APIs within the Salesforce org. It allows administrators and developers to browse, search, and discover APIs exposed by the platform, custom Apex REST services, and external services registered in the org.
Real-World Example
A new developer at Helios Financial opens the API Catalog in Setup to find existing REST endpoints built by previous developers. She discovers a custom Apex REST service for credit score lookups and an external service for address verification, allowing her to reuse these APIs in her new integration instead of building them from scratch.
Why API Catalog Matters
The API Catalog solves a critical discoverability problem in Salesforce organizations. As orgs mature, developers, ISVs, and system integrators create numerous custom Apex REST services, platform events, and register external services for third-party integrations. Without a centralized registry, new team members or developers from other departments waste time recreating APIs that already exist, duplicate efforts occur, and institutional knowledge about available integrations remains siloed. The API Catalog provides a single, searchable source of truth in Setup where all available APIs—including Salesforce standard REST APIs, SOAP APIs, custom REST endpoints, and registered external services—are cataloged and documented, enabling API reuse and reducing redundant development work.
As organizations scale, the absence of proper API Catalog governance leads to significant problems: API sprawl occurs without visibility, multiple teams build competing solutions for the same business need, API versioning becomes chaotic, and integration projects experience delays while developers hunt for existing capabilities. Teams may inadvertently publish APIs without proper documentation or ownership information, creating technical debt. In enterprise environments with hundreds of custom integrations, a well-maintained API Catalog becomes essential for managing API lifecycle, preventing orphaned endpoints, ensuring compliance with naming conventions, and enabling cross-functional teams to discover and trust available APIs. This governance becomes especially critical when multiple development teams operate across different business units or when API security and rate limiting must be audited and enforced organization-wide.
How Organizations Use API Catalog
- Helios Financial Services — Helios needed to consolidate integrations across retail, commercial, and wealth management divisions. Their API Catalog revealed that three separate teams had built different credit verification APIs for the same core function. By discovering these duplicates through the catalog, they consolidated to a single, well-documented REST endpoint, eliminated maintenance burden on two legacy APIs, and reduced integration testing time by 40%. New developers onboarding to any division now consult the API Catalog first, preventing future duplication.
- CloudPath Healthcare Systems — CloudPath maintains integrations with 15 different healthcare providers and internal systems (ERP, HIPAA-compliant document storage, patient portals). Their API Catalog serves as the single source of truth for all REST endpoints and external services, including which APIs require OAuth2 versus JWT authentication, rate limits, and compliance certifications. During their annual security audit, the API Catalog enabled them to quickly identify all external-facing APIs, verify that each had proper authentication and logging, and demonstrate compliance to regulators without conducting a manual code review across multiple repositories.
- Meridian Retail Enterprises — Meridian uses their API Catalog not just for discovery but as a living documentation system. When they migrated from an older REST API version to a new version, they used the catalog to track which internal applications and third-party integrations were still consuming the deprecated endpoint. This visibility allowed them to execute a controlled deprecation process, notify dependent teams 90 days in advance, and prevent production outages that might have occurred with a surprise API shutdown. The catalog's search and filtering capabilities made the migration project timeline visible and manageable.