Skip to main content

Webhooks Overview

Webhooks are a system-to-system communication tool that use a push-based strategy to send HTTP callbacks for events happening in the Mambu application.

For example, you can set up a webhook to notify one of your applications that a loan has been disbursed. When the event occurs, Mambu sends an HTTP request (typically POST) to your endpoint with a payload that can include details such as the loan account ID, client information, and amount. Your application can:

  • Process the request directly, or
  • Call back to Mambu to retrieve additional information or trigger further actions (for example, creating a task or sending an email), or
  • Enrich the data and forward it to another partner service.

For more information on setting up webhooks, see Create webhook templates.

note

The Streaming API is another system-to-system communication tool, but it uses a pull-based strategy and is better suited for use cases where multiple client applications must consume large volumes of data from Mambu. For more information, see Streaming API in our User Guide and Streaming API in our API Reference.

Character recognition

The Mambu application works best with only alphanumeric characters. Other types of characters such as emoji are not supported and clients should ensure some kind of validation on their side.

To be clear, any characters from the following lists cannot be used when writing text fields on the Mambu UI and API:

Benefits of using webhooks​

Audit​

The communication history records every notification sent out.

  • Each webhook notification is stored with its destination, status, timestamps, and the payload as it was rendered at send-out time.
  • When you manually re-send a failed webhook, the stored payload for that notification is sent again (it is not re-computed from the current template).

This makes it easier to diagnose issues and, when needed, re-send exactly what was originally produced.

Assured delivery​

Webhook delivery is backed by a retry mechanism that uses an exponential backoff policy.

  • If a webhook cannot be delivered (for example, due to timeouts, network errors, or non-2xx responses), the system may retry delivery according to a configured backoff policy.
  • Only HTTP 2xx responses are considered successful. Non-2xx responses, timeouts, and connection errors are recorded as failures and may be retried depending on configuration.

If automatic retries are exhausted or not applicable, no further automatic attempts are made. You can manually re-send failed webhook notifications via the UI or via API where available. For more information about Mambu APIs in general,