Skip to main content

Explore API-Led Connectivity

Learning Objectives

After completing this unit, you’ll be able to:

  • Explain API-led connectivity and its role in modern IT solutions.
  • Describe the three-layer API architecture.
  • Understand how API-led connectivity enables reuse, agility, and self-service.

Build Smarter Connections

In the previous unit, you learned how application networks create a flexible and scalable way to connect systems using APIs. Now, it’s time to dive deeper into how this happens. Specifically, how API-led connectivity transforms networks into structured, reusable frameworks that help save time and resources.

The Three-Layer API Architecture

API-led diagram with three layers: Experience APIs (airport kiosk, mobile app, web browser), Process API (flights data orchestration), and System APIs (American, United, Delta flight data services).

API-led connectivity organizes APIs into three distinct layers, each serving a specific purpose.

1. System APIs

System APIs connect directly to core systems like databases, ERPs, or CRMs, unlocking data and processes that were previously siloed. These APIs act as the foundation of your integrations, ensuring stability while shielding systems of record from disruption.

  • Example: A System API for Salesforce exposes customer data for other applications to access without impacting the CRM’s operations.

2. Process APIs

Process APIs orchestrate and process data from multiple System APIs and other Process APIs, creating reusable business logic that meets specific organizational needs. These APIs enable data transformation, aggregation, and enrichment to serve different use cases.

  • Example: A Process API combines customer data from Salesforce and order data from an eCommerce platform to provide a unified view for reporting.

3. Experience APIs

Experience APIs deliver data in formats optimized for user interfaces or devices. They adapt the output of Process APIs for specific consumption needs, such as a mobile app or dashboard.

  • Example: An Experience API serves a mobile app with real-time order updates, including tracking and delivery status.

This layered approach ensures that APIs are modular, reusable, and easy to scale as business demands evolve.

The Real-World Benefits of API-Led Connectivity

API-led connectivity revolutionizes how organizations deliver solutions by:

  • Enabling Reuse: Teams can repurpose existing APIs, reducing duplication and accelerating development.
  • Boosting Agility: Modular APIs allow businesses to adapt quickly to new opportunities and challenges.
  • Fostering Self-Service: Developers across teams can easily discover and consume APIs, reducing dependency on central IT.
  • Enhancing Security and Governance: APIs are designed to be secured and monitored, providing IT with visibility and control.

Test Your Knowledge

Match each API layer (System, Process, Experience) with its description and an example use case.

Behind the Transformation at Mule United Airport

In Unit 1, you saw how Mule United Airport (MUA) overcame operational challenges by implementing an application network. Next, you take a closer look at how API-led connectivity powered that success.

The MUA developer, Alex, faced the task of integrating customer data, booking systems, and inventory databases. The goal? To streamline operations and improve passenger experiences while building a foundation for future scalability.

The Decisions Behind the Solution

Alex chose the API-led connectivity approach to ensure that integrations were reusable, secure, and adaptable. This decision let MUA move away from rigid, point-to-point connections and instead create a modular architecture. Here’s how the solution was designed.

  • System APIs
    • Why? To unlock core data from siloed systems like the airport’s CRM, flight booking platform, and inventory database.
    • How? APIs were created to expose only the necessary data securely, protecting the systems of record from disruption.
  • Process APIs
    • Why? To orchestrate and aggregate data into meaningful services, making it reusable across multiple applications.
    • How? A Process API was designed to merge customer data with flight schedules and real-time inventory, enabling business logic for services like passenger notifications and gate management.
  • Experience APIs
    • Why? To tailor the aggregated data into formats optimized for specific user experiences.
    • How? APIs were built to deliver mobile-friendly data for passengers and web-based dashboards for airport staff.

The Implementation

Using the three-layer API architecture:

  • System APIs accessed real-time data without burdening the underlying systems, ensuring reliability.
  • Process APIs transformed raw data into actionable insights, enabling seamless collaboration between the booking platform and inventory database.
  • Experience APIs provided consistent and responsive interfaces for the airport’s mobile app and website.

The Results

By leveraging API-led connectivity, MUA achieved:

  • Faster Development Cycles: Developers reused existing APIs to quickly roll out new features.
  • Improved Passenger Experiences: Real-time updates reduced uncertainty and enhanced satisfaction.
  • Future Scalability: Adding new systems, like an airline partner or baggage tracking, required minimal effort thanks to the reusable API framework.
  • Future Flexibility: Experience APIs positioned MUA to adapt data for new interfaces—like AI-driven chatbots, voice assistants, and predictive notifications—allowing for expansion into emerging technologies.

Next up, explore how reusable APIs and application networks empower teams to innovate at speed while maintaining governance and security.

Resources

Share your Trailhead feedback over on Salesforce Help.

We'd love to hear about your experience with Trailhead - you can now access the new feedback form anytime from the Salesforce Help site.

Learn More Continue to Share Feedback