Process API
In MuleSoft's API-led connectivity approach (part of the Salesforce ecosystem), a middle-tier API that orchestrates data between system APIs and experience APIs, handling business logic, data transformation, and process coordination.
Definition
In MuleSoft's API-led connectivity approach (part of the Salesforce ecosystem), a middle-tier API that orchestrates data between system APIs and experience APIs, handling business logic, data transformation, and process coordination.
In plain English
“A Process API in MuleSoft's API-led connectivity is a middle-tier API that orchestrates data between system APIs (which expose raw system data) and experience APIs (which deliver data to specific channels). Process APIs handle business logic, data transformation, and process coordination.”
Worked example
Vellum Capital's MuleSoft API platform follows API-Led Connectivity. A Process API called CustomerOnboardingProcess orchestrates the multi-step onboarding workflow: it consumes data from three System APIs (Salesforce CRM, the credit bureau, the legal entity system), applies the business rules (KYC checks, eligibility scoring, account creation), and exposes the orchestrated result to Experience APIs that serve the mobile app and web portal. The Process API is the middle tier - neither raw system data nor channel-specific delivery - embodying the company's onboarding business logic. When the rules change, Process APIs are where the change lands.
Why Process API matters
In MuleSoft's API-led connectivity approach (part of the Salesforce ecosystem), a Process API is a middle-tier API that orchestrates data between system APIs and experience APIs, handling business logic, data transformation, and process coordination. The three-tier model includes System APIs (raw data access from individual systems), Process APIs (business logic and orchestration), and Experience APIs (channel-specific data delivery), with Process APIs serving as the integration glue.
Process APIs are valuable because they encapsulate business logic that would otherwise be duplicated across consumers. Multiple Experience APIs can call the same Process API for shared business logic, ensuring consistency and reducing duplication. Mature MuleSoft architectures invest in Process API design carefully, treating them as the layer where business rules and data transformation logic live. This separation of concerns is core to API-led connectivity's value proposition.
How organizations use Process API
Built process APIs that orchestrate data from multiple system APIs into unified business views consumed by experience APIs.
Uses process APIs to encapsulate business logic, ensuring multiple experience APIs share the same consistent rules.
Treats process API design as core architecture work in MuleSoft deployments.
Trust & references
Straight from the source - Salesforce's reference material on Process API.
- API-Led Connectivity OverviewMuleSoft Documentation
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is a Process API?
Q2. What are the three API tiers?
Q3. Why use process APIs?
Discussion
Loading discussion…