# API-led connectivity layers and benefits

*MuleSoft Developer Study Guide · Creating Application Networks · Last updated October 28, 2026 · https://www.certifyforce.com/study-guide/mulesoft-developer/creating-application-networks/api-led-connectivity-layers-and-benefits*

What System, Process and Experience APIs each own, how to place new orchestration or formatting logic in the right layer, and the reuse, agility, self-service and governance benefits that API-led connectivity delivers.

- Certification: Salesforce MuleSoft Developer
- Exam section: Creating Application Networks
- Study guide: https://www.certifyforce.com/study-guide/mulesoft-developer

**Official exam objective:**

> Identify features of an API-led approach.

## What the exam expects

- Match System, Process and Experience APIs to their responsibilities and reject options that put a job in the wrong layer.
- Decide where new logic belongs: combining data from several sources goes in a Process API; shaping output for one consumer goes in an Experience API.
- Diagnose a design that buries back-end access or business rules in an Experience API and so blocks reuse.
- List the benefits API-led connectivity delivers (reuse, agility, self-service, security and governance) and reject claimed benefits that contradict them.

Key terms:
- **API-led connectivity**: a methodical way to connect data to applications through reusable and purposeful APIs.
- **System API**: unlocks data from a core system of record and shields it from consumers.
- **Process API**: orchestrates System APIs and other Process APIs into reusable business logic.
- **Experience API**: adapts Process API output for a specific interface such as a mobile app or portal.

## Key facts

| Fact | Detail | Source |
|---|---|---|
| Three layers | System, Process, Experience | [API-Led Connectivity Essentials](https://trailhead.salesforce.com/content/learn/modules/application-networks-and-api-led-connectivity-in-mulesoft/explore-api-led-connectivity) |
| System API connects to | Core systems such as databases, ERPs, CRMs; shields systems of record | [API-Led Connectivity Essentials](https://trailhead.salesforce.com/content/learn/modules/application-networks-and-api-led-connectivity-in-mulesoft/explore-api-led-connectivity) |
| Process API calls | Multiple System APIs and other Process APIs | [API-Led Connectivity Essentials](https://trailhead.salesforce.com/content/learn/modules/application-networks-and-api-led-connectivity-in-mulesoft/explore-api-led-connectivity) |
| Process API examples | Customer 360 view, order fulfillment, shipment status | [Types of APIs](https://www.mulesoft.com/api/types-of-apis) |
| Experience API input | Adapts Process API output for a specific consumer | [API-Led Connectivity Essentials](https://trailhead.salesforce.com/content/learn/modules/application-networks-and-api-led-connectivity-in-mulesoft/explore-api-led-connectivity) |
| New channel on existing layers | Rewiring instead of recreating | [What Is API-led Connectivity?](https://blogs.mulesoft.com/learn-apis/api-led-connectivity/what-is-api-led-connectivity/) |
| Self-service benefit | Developers discover and consume APIs, less dependency on central IT | [API-Led Connectivity Essentials](https://trailhead.salesforce.com/content/learn/modules/application-networks-and-api-led-connectivity-in-mulesoft/explore-api-led-connectivity) |
| Security benefit | APIs are secured and monitored; IT keeps visibility and control | [API-Led Connectivity Essentials](https://trailhead.salesforce.com/content/learn/modules/application-networks-and-api-led-connectivity-in-mulesoft/explore-api-led-connectivity) |
| Reported averages | 64% productivity, 78% faster launches, 74% lower maintenance costs | [3 customer advantages](https://www.mulesoft.com/api/advantages-of-api-led-connectivity) |

## Check yourself

- Why can many teams use a System API without learning the system behind it?
- Why do Process APIs not need to worry about where data originates or how it is delivered?
- Which two sources does Trailhead's Mule United Airport Process API merge with real-time inventory?
- When teams adopt API-led connectivity, what does MuleSoft's blog say a new initiative does with existing building blocks instead of building solution components?

## Sources

- [Understanding API-Led Connectivity Essentials (Trailhead unit)](https://trailhead.salesforce.com/content/learn/modules/application-networks-and-api-led-connectivity-in-mulesoft/explore-api-led-connectivity)
- [Types of APIs and how to determine which to build](https://www.mulesoft.com/api/types-of-apis)
- [What Is API-led Connectivity?](https://blogs.mulesoft.com/learn-apis/api-led-connectivity/what-is-api-led-connectivity/)
- [3 customer advantages of API-led connectivity](https://www.mulesoft.com/api/advantages-of-api-led-connectivity)
- [What is an application network?](https://www.mulesoft.com/resources/api/what-is-an-application-network)

## About the full unit

The "Core concepts", "Exam traps" and "Worked scenario" sections of this unit, its 6 linked practice questions, and unlimited timed mock exams are included with the MuleSoft Developer pack (USD $19): https://www.certifyforce.com/practice-exams