A success story of establishing API catalog to achieve better reusability
API Catalog to Improve and Inspire Reusability
TELECOMMUNICATIONS
At a glance
CHALLENGES
- Lack of discoverability & reusability.
- Lack of standardization of APIs.
- Duplication of APIs and integrations.
- Management and monitoring were not easy.
BENEFITS
- Created a centralized API catalog.
- Established API governance with standards and guidelines.
- Provided developer support through a developer portal.
- Implemented API management tools with monitoring and analytics capabilities.
- Paved the way for API monetization.
PLEKTONLABS SERVICES
- Service 1
- Service 2
RESULTS
- Centralized API catalog.
- Better Developer Support.
- Holistic view of integrations.
CTA WITH SERVICE OR 1 END RESULT
Problem
This story is about renowned multinational telecommunication holding company who offers various products and services and has a complex IT system with a large number of internal and external MuleSoft APIs for communication between systems and applications. They faced challenges with its APIs, including difficulty in discovery, access, standardization, management and maintenance, resulting in a fragmented API landscape and hindrance for new app development.
Solutions
As a solution they established an API strategy to improve the discovery, standardization, and management of their APIs. This included creating a centralized API catalog, establishing API governance, providing developer support through a portal, and establishing MuleSoft API management with monitoring and analytics capabilities.
MuleSoft Anypoint Community Manager (ACM) was integrated with hundreds of business groups in MuleSoft Anypoint platform with their company to fetch all the APIs and assets from Exchange and established the catalog. The API catalog was further integrated with Azure AD, MuleSoft Access Management, ServiceNow to manage identity, access control, authentication, authorization and to associate project information.
