A Mule application exposes an API for creating payments.

A production health endpoint should verify the same network path and HTTP infrastructure that clients depend on. Reusing the API's existing HTTP Listener configuration and port ensures that the health check validates whether the application's actual inbound listener is operational. Mule HTTP Listener configurations define the host, port, protocol, TLS configuration, and potentially a common base path; multiple listener sources can use the same configuration while exposing different paths.

A separate listener and port could report healthy even when the primary API listener is unavailable or incorrectly configured, producing a misleading health signal. Sending health information outward to another system is telemetry rather than an endpoint-level availability test. Likewise, exercising a payment API with genuine customer payment data is inappropriate because monitoring should be non-destructive and should not create business transactions.

Therefore, a lightweight endpoint such as /health using the same listener configuration provides a representative indication that the application can receive traffic through its normal production interface without invoking payment-processing behavior.

Reference topics: Mule HTTP Listener configuration; production health checks; API availability monitoring; non-invasive operational endpoints.

Official documentation: https://docs.mulesoft.com/http-connector/latest/http-listener-ref

===============================================================