At the Murex Client Hackathon, MX.3 REST APIs, AI Inspire Teams to Develop Novel Solutions

by François-Boris de Mijolla, Murex head of FX, equity derivatives and model integration in EMEA client services

In June 2026, Murex welcomed 60 clients to its Paris headquarters for a two-day, focused hackathon. The idea was to put our latest generation of REST APIs in client hands. We wanted them to explore real world scenarios, get started quickly and turn ideas into working use cases. The hackathon—its energy, the teamwork it necessitates and fosters, its pace, the immediate proximity it creates with client teams—was an inspiring, condensed, intense event.

In my experience, financial institutions aim to keep most business processes streamlined and standardized, while introducing customizations only where they truly add value.

At the hackathon, clients explored building on core MX.3 capabilities and extending them through our latest REST APIs to address their own specific needs.

Designed around open standards, Murex REST APIs provide secure, real time access to MX.3 data and functionality across front to back workflows. Murex REST APIs make it straightforward to integrate, automate processes and extend the MX.3 platform within a broader ecosystem.

Murex REST APIs are developer friendly by design, with OpenAPI specifications, detailed documentation and ready to use tools, and allow developers and teams to prototype and iterate quickly. Combined with AI, this created a powerful dynamic at the hackathon. Teams moved from ideas to working use cases in a matter of hours. In some cases, the progression happened without even writing much code.

The Murex Client Hackathon brought together client teams from across the EMEA region, representing 10 different countries. With a mix of functional and technical profiles, each team set out to turn their ideas into a working prototype within just 24 hours.

What stayed with me was how closely the ideas were tied to real situations. Clients worked through challenges they face every day and used AI to rethink how to address them.

Below are several examples that stood out to me:
• A bank manages the trade confirmation process using an AI assistant to help back officers spot differences and prioritize their work.
• A bank builds an advanced verification engine for market-sensitive curves to eliminate the risk of traders quoting off market.
• An asset manager implements a custom Benchmark Rebalance Optimizer to enhance performance and reliability of this critical process for portfolio managers.
• A risk officer builds an application extracting historical risk measures from MX.3 (e.g., XVA, SA-CCR, IM, FRTB, etc.) and gives the ability to slice and dice through snapshots exploring trends, explaining outliers and eventually enabling a data analytics approach.

What these use cases had in common was their reliance on MX.3 as a central source of data across trading, risk and operations. The integrated platform hosts business processes across financial institutions. By exposing that data and functionality through REST APIs, teams accessed, combined and extended them directly within their own applications.

This made it possible to plug MX.3 into broader workflows, automate processes and build new interfaces, whether for traders, risk managers or operations, without data duplication or rethinks of existing processes. In practice, APIs act as a simple, consistent way to build on top of MX.3 and keep its core strengths of data integrity, analytics and workflow coverage centered.

To reemphasize, client prototypes were built in a 24-hour window at the hackathon. How is this possible?

MX.3 REST APIs have been designed with a strong focus on usability. Besides, they are documented based on the Open API standard. This allows developers to understand swiftly how the API works and what it can do. Through its Developer Portal, Murex provides codelabs and mock servers to directly experience MX.3 REST APIs. A few self-training hours suffice before being able to leverage them. During the hackathon, individual teams could mobilize APIs with little preparation. Teams moved nimbly. One team even decided to add a new API just an hour before the demo. They nailed it, by the way.

Many client teams used AI, especially those teams that never coded on MX.3 REST APIs before. This is made easy thanks to the Open API documentation, whose format is also consumable by AI. So what? Teams were able to build an entire prototype, sometimes without even writing a single line of code.

A huge collaboration effort was necessary to make the event a success and a positive experience for clients. We aimed to do this from a technical point of view, but also from a human perspective. One participant told me, unprompted: “This is the best hackathon I did… and I’ve done a few!” The hackathon created new bonds between Murex experts and client teams. Everyone had fun, gained experience and got inspired. This hackathon brought a new definition of what’s possible to do with MX.3.