System APIs
Encapsulate system-specific access and expose stable contracts over Salesforce, Oracle, databases or other platforms.
Reusable APIs forconnected enterprise systems.
API-led connectivity separates system access, business orchestration and consumer experience concerns so integrations stay reusable as the business changes.
Process APIs
Compose reusable business logic and coordinate data across system boundaries without coupling every consumer to every source.
Experience APIs
Shape data for a particular consumer while preserving the reusable integration layers beneath it.
API-led connectivity organises integrations into three layers. System APIs unlock data from Salesforce, SAP, Oracle or databases behind stable contracts. Process APIs compose that data into business capabilities such as orders, customers or patients. Experience APIs shape it for a specific channel: mobile, web or partners.
Prince applied this pattern on the Oracle PeopleSoft to Salesforce programme and across his HCLTech delivery. It makes new consumers cheaper to add and isolates change when a backend system is upgraded.
The layers are a tool, not a rule: he collapses them where the reuse is not real, and documents why.
Frequently asked
What are System, Process and Experience APIs?
System APIs expose a backend system, Process APIs orchestrate business logic across systems, and Experience APIs tailor data for a specific consumer or channel.
What are the benefits of API-led connectivity?
Reuse, faster delivery of new channels, isolation of backend changes, clearer ownership and better governance of integrations across the organisation.