| Table of Contents | ||
|---|---|---|
|
...
MifosX will send along a few HTTP headers to differentiate between event types.
| Name | Description |
|---|---|
| X-Mifos-Entity | The entity type that was triggered. |
| X-Mifos-Action | The action triggered on the entity type. |
| X-Mifos-Platform-TenantId | The tenant which experienced the event. |
The bridge / third-party app is expected to authenticate with the MifosX server first and send the auth token along with each request to fetch additional information such as client's mobile number or account number.
See /hooks/template response (groupings array inside the json) or the m_permission table (other than special, read and checker permissions) to find a list of all available combinations of Entity and Action.
List hooks
https://demo.openmf.org/api-docs/apiLive.htm#configs_hooks_retrieve
...