Developer Overview
- 26 Jan 2022
- 4 Minutes To Read
-
Print
-
DarkLight
-
PDF
Developer Overview
- Updated On 26 Jan 2022
- 4 Minutes To Read
-
Print
-
DarkLight
-
PDF
Developing with Mambu
In keeping with our philosophy of composable banking, Mambu provides many avenues allowing you to develop software to interact with our services and features.
Mambu APIs
Mambu offers a full suite of RESTful APIs to provide programmatic access to nearly every aspect of our banking software, typically with JSON or YAML requests.
Our APIs include:
- API v2: APIs for our core banking platform.
- API v1: Our legacy core banking API.
- Payments API: For making and receiving payments, mapping accounts to IBAN, Anti Money Laundering, and more.
- Streaming API: An enterprise feature which allows customers to set up configurable event feeds that can be used to power your own banking ecosystem.
- MPO API: An enterprise package which acts as a middle layer between different systems to pull, process, and push data via APIs. MPO has its own independent Remote Procedure Call API.
For more information, view the API reference documentation linked above, or see Mambu APIs.
Webhooks
Mambu supports highly-configurable webhooks, which may be used as user-defined callbacks triggered when your specified conditions are met by the cloud banking platform. For example, you may configure a webhook to POST a custom payload to your application whenever a loan account goes into arrears.
For more information, see Webhooks.
Mambu Ecosystem
The Mambu Ecosystem extends Mambu core banking by providing an independent enterprise orchestration layer, the Mambu Process Orchestrator (MPO), to facilitate your interactions with any number of third-party services.
We provide a large and growing number of Connectors, which you can drop into MPO and configure to easily manage interactions with third-party providers of services such as payment processing, anti-money laundering, loan origination, Know Your Customer, and more.
For more information, see our Ecosystem Documentation.
Configuration as Code
Configuration as Code (CasC) allows you to quickly configure new instances, standardize and migrate configuration between tenants, and duplicate configuration settings for multiple sandboxes.
With CasC, you may batch configure supported Mambu elements such as organization details, custom fields, holidays, branches, user roles, and more via the API. This allows you to get or set multiple configuration settings for a supported element with a single API call per tenant.
For more information, see Configuration as Code.
Mambu Apps
Mambu Apps allow partners and developers to extend Mambu's capability and to add value with little effort. Apps are defined in a simple XML file - the definition includes general information about the application as well as specific endpoints and extension point which will define how the app is shown in Mambu.
For more information, see Building Apps.
Jasper Reports
JasperReports is a powerful open source reporting tool that has the ability to deliver rich content onto the screen, to the printer, or to a variety of supported file formats. Jasper reports can be built to work with Mambu using a few simple steps.
For more information, see Jasper Custom Reports.
Frequently Asked Questions
How do I develop & test my apps?
How do I develop & test my apps?
We highly recommend using our Sandbox environment. Every partner and paying organization has access to a second environment where they can freely develop and test against APIs. This gives you a safe environment where you can try out new APIs, test changes and experiment with new ideas.
Do you have wrapper libraries?
Do you have wrapper libraries?
Our APIs are constantly being improved to add endpoints and features, and we generally recommend using a lightweight API client to access our APIs. This will make it easier to update and customize your API usage for only the operations you are interested in.
However, we do provide an open source Java wrapper library at our GitHub space, and you may download SDKs in a variety of languages. For more information on our SDKs, see Tenant API Reference in our API Reference guide.
How is version control handled?
How is version control handled?
We currently do not support versioning. However, APIs are backward-compatible for at least one release and we announce any changes with our release notes. This means you'll have up to 6 months to change over from any modified APIs. See Mambu Release Cycle for more information.
How are new features rolled out?
How are new features rolled out?
We are constantly adding more functionality and improving the performance of our APIs with every release of Mambu. You can stay up to date on new features with our release notes, which are published on our Mambu Community site. If you have any specific questions or requests about the API roadmap, please contact us.
How can I check if a Mambu server is available?
How can I check if a Mambu server is available?
The /healthcheck endpoint is a convenient way to manually or automatically check the status of a specific Mambu server. If the Mambu server is available, it will return response code 200 together with the message OK. You can enter the URL into a web browser or call the API using your tool of choice. Visiting our status page will also provide you with real-time information and metrics on all our servers, more information can be found in our Mambu status support page.
Tenant URL and endpoint
https://TENANT_NAME.mambu.com/healthcheck
Request
GET https://TENANT_NAME.mambu.com/healthcheck
Responses
| Response Code | Text | Description |
|---|---|---|
| 200 | OK | Server is functioning properly |
| 500 | Internal Server Error | Server is not available |
If you have a question about how anything works or have come across something you haven't seen explained here, get in touch with our community of fellow users and Mambuvians where someone will lend a hand.
Was this article helpful?
