In which context is the term "System API" typically used in MuleSoft?

The term "System API" is typically used in MuleSoft to refer to a service layer that provides core functionalities and exposes important business logic to other systems. System APIs act as a bridge between the underlying systems, such as databases or external services, and the business logic applications that require that data or functionality. This enables a layer of abstraction that isolates the underlying data sources and allows for better governance, security, and scalability.

By defining a clear service layer for core functionalities, organizations can manage their APIs more effectively, allowing for reuse, easier maintenance, and standardized access across different applications and services. This architecture is aligned with the MuleSoft best practices of API-led connectivity, where System APIs play a critical role in enabling communication between various applications while ensuring consistency and reliability in how data is accessed and manipulated.

The other contexts provided do not accurately represent the role of a System API, as they focus on user interfaces or direct data entry mechanics rather than the foundational service layer that System APIs represent within the broader architecture.