Using the Apache Fineract batch API
Combining several Fineract API calls into one request: enclosing them in a single transaction, referencing results of earlier requests, error behavior and when batch calls beat many single calls.

Building on Fineract's REST API and extending it without forking: batch requests, idempotency, generated clients, custom modules, jobs, business steps, processors, events and testing.
Combining several Fineract API calls into one request: enclosing them in a single transaction, referencing results of earlier requests, error behavior and when batch calls beat many single calls.
Making repayments and disbursements safe to retry: sending an idempotency key header, how Fineract matches action and entity, cached results and HTTP 409 on in-progress duplicates, and idempotency inside batch requests.
Producing typed clients for Fineract: the OpenAPI 3.0.3 specification, building fineract-client.jar, generating clients for other languages and keeping clients in step with each release.
Extending Fineract without editing core sources: the custom folder convention, starter auto-configuration, replaceable services, packaging modules into your image and keeping them compatible across upgrades.
Adding your own scheduled jobs: Spring Batch job and tasklet definitions, the database migration that registers the job, job name configuration and deployment in a custom module.
Adding country or institution specific end-of-day logic to the Loan COB job: implementing a business step, registering it with a database migration and ordering it through the steps API.
Implementing your own repayment allocation logic: writing a transaction processor, overriding the processor factory and testing allocation against existing products before production.
Adding or enriching events that Fineract publishes: new BusinessEvent classes, Avro schemas in fineract-avro-schemas, bigdecimal fields, and higher-priority custom serializers for existing events.
Building a regression suite for a customized Fineract: Cucumber end-to-end tests, integration tests against a running backend, business date control and test data for loans, accounting and COB.
Planning staff or customer apps on headless Fineract: starting from the Mifos X web app or building your own, tenant headers, authentication, API paging and keeping self-service APIs out of public apps.

Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.