Over the past few months, several new integrations and API clients have been developed and released. This news post provides an overview of these developments.

Integrations

OutSystems

Back in August, a user asked us if it would be possible to integrate mosparo into OutSystems, an AI-powered low-code platform. We started testing OutSystems and trying to find a way to integrate mosparo. After an early proof-of-concept, we were confident that we could offer an integration. We began to build a real integration. Because the integration was not straightforward, we needed some time to complete all the required steps, including building and releasing the .NET API client that powers the integration.

After all this time, the integration and the API client is now finally available in OutSystems Forge. The mosparo API client is required to verify the submission. The mosparo Integration is a reactive module to add mosparo to your form.

TYPO3

Some months ago, in June, we received the question of whether it would be possible to integrate mosparo into TYPO3. Digi92, a long-time contributor to mosparo, announced that work on an integration with TYPO3 has already begun. Some weeks later, denkwerk GmbH released an official integration for TYPO3 (EXT:form and Extbase-based forms). Digi92 released an additional extension for EXT:powermail.

At the same time, developers from SICOR IT GmbH began developing an additional integration for TYPO3 and EXT:powermail.

You can find more information about the integrations here:

API clients

Go API client (gosparo)

In June, deBarbarinAntoine took the time to build an API client in Go to verify the mosparo request. You can find all the details about this library here: https://github.com/debarbarinantoine/gosparo

.NET API client

The OutSystems integration relies on server-side logic written in C# and the .NET Framework. For this, we had to develop the required verification logic in C#. In the prototype, we added it directly to the OutSystems integration. But for the official version, we needed to add it more effectively. For this, we’ve developed the .NET API client and released it on NuGet. The API client is available here: https://www.nuget.org/packages/Mosparo.ApiClient.

You can use this library in other .NET projects, as it does not rely on OutSystems and has only two dependencies (System.Net.Http and System.Net.Json).

Thank you very much for your contributions and the time you invested in developing integrations and API clients.

If you have trouble with the integrations or find any issues, please create an issue in the official repositories or start a new discussion in the GitHub discussions. Would you like to use mosparo in a system where no mosparo integration is currently available? Your suggestions are always welcome in the Integration category of GitHub discussions.