# Health endpoints for Mule applications

*MuleSoft Developer II Study Guide · Implement monitorable Mule applications · Last updated November 7, 2026 · https://www.certifyforce.com/study-guide/mulesoft-developer-ii/implement-monitorable-mule-applications/health-endpoints-for-mule-applications*

Design reachable health endpoints whose response contracts reflect application outcomes, with correct listener routing, response encoding and input timeouts.

- Certification: Salesforce MuleSoft Developer II
- Exam section: Implement monitorable Mule applications
- Study guide: https://www.certifyforce.com/study-guide/mulesoft-developer-ii

**Official exam objective:**

> Expose Health Check endpoints from a Mule application.

## What the exam expects

- Expose a dedicated health endpoint with an explicit probe contract.
- Separate listener address and route configuration from response generation.
- Match healthy and unhealthy responses to the flow's actual outcome.
- Choose response streaming and incoming-data timeout controls deliberately.

A **listener** receives HTTP requests; a **base path** prefixes its routes; a **probe** is a monitoring client; a **response contract** defines the status and representation the client interprets. The HTTP details here use Connector1.9, alongside Mule4.6 error handling.

## Key facts

| Fact | Detail | Source |
|---|---|---|
| Managed readiness | Worker CloudHub checks the Mule Agent endpoint. | [CloudHub monitoring](https://docs.mulesoft.com/cloudhub/worker-monitoring) |
| Business health | The application must implement the required dependency check. | [CloudHub monitoring](https://docs.mulesoft.com/cloudhub/worker-monitoring) |
| Listener base path | Applies to listeners referencing that configuration. | [Listener source](https://raw.githubusercontent.com/mulesoft/docs-connectors/33276ccdb80668dd8bd45102a529a5fcc0918eea/http/1.9/modules/ROOT/pages/http-listener-ref.adoc) |
| Path choice | A specific path outranks a wildcard match. | [Listener source](https://raw.githubusercontent.com/mulesoft/docs-connectors/33276ccdb80668dd8bd45102a529a5fcc0918eea/http/1.9/modules/ROOT/pages/http-listener-ref.adoc) |
| Continued error | The owning scope completes successfully. | [On Error scopes](https://docs.mulesoft.com/mule-runtime/4.6/on-error-scope-concept) |
| Propagated error | The owning scope fails. | [On Error scopes](https://docs.mulesoft.com/mule-runtime/4.6/on-error-scope-concept) |
| Response NEVER | Determines the outgoing content length, consuming streams if needed. | [Listener source](https://raw.githubusercontent.com/mulesoft/docs-connectors/33276ccdb80668dd8bd45102a529a5fcc0918eea/http/1.9/modules/ROOT/pages/http-listener-ref.adoc) |
| Input read timeout | Bounds waiting for further request data. | [HTTP1.9 reference](https://raw.githubusercontent.com/mulesoft/docs-connectors/33276ccdb80668dd8bd45102a529a5fcc0918eea/http/1.9/modules/ROOT/pages/http-documentation.adoc) |

## Check yourself

- Why can a connector supply an error reason phrase without a custom expression?
- When does persistent-connection idle timeout apply?
- What happens to a connection after its first completed request if persistence is disabled?

## Sources

- [HTTP Listener source, HTTP1.9](https://raw.githubusercontent.com/mulesoft/docs-connectors/33276ccdb80668dd8bd45102a529a5fcc0918eea/http/1.9/modules/ROOT/pages/http-listener-ref.adoc)
- [HTTP Connector1.9 reference](https://raw.githubusercontent.com/mulesoft/docs-connectors/33276ccdb80668dd8bd45102a529a5fcc0918eea/http/1.9/modules/ROOT/pages/http-documentation.adoc)
- [CloudHub application monitoring](https://docs.mulesoft.com/cloudhub/worker-monitoring)
- [On Error scope, Mule4.6](https://docs.mulesoft.com/mule-runtime/4.6/on-error-scope-concept)

## About the full unit

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