Welcome to maesn!

We do the hard integration work of normalizing data across a multitude of ERP and Accounting systems into a unified schema.

If you have any questions, don’t hesitate to reach out to us via support[at]maesn.com. Access to the API can be requested via our website.

​

What is maesn?

​maesn is the only Unified API that provides standard endpoints tailored for ERP use cases. We will continuously work on improving and extending our portfolio of use cases and ERP systems that we offer easy integration to.

Beside great use-cases, the most relevant ERP systems and the best possible support, we provide several technical key features that enable you to accelerate your integration game:

• Drop-in frontend authentication components that makes it easy to connect to your customers’ end systems.
• Authenticated pass through request for the occasional API endpoint not included in our common data models.
• Templates for you docs, so that you have all content for your end user-onboarding ready
• Soon: Observation dashboard to monitor all connections and integration activities, as well as an outstanding 1st level support with our wiki

Once you get started with maesn and integrate with our endpoints, you automatically have support for all existing and new integrations we add.

​

Unified API

A Unified API provides a standardized set of endpoints for accessing data and functionality across multiple systems within the same software vertical (such as Accounting or Warehouse Management). By providing a single point of connection, Unified APIs act as an abstraction layer that simplifies authentication, data transformation, syntax, and data synchronization.

The point of Unified APIs is to make it easier for developers to build integrations with multiple similar software products, e.g., for a spend management system to provide integrations to a range of accounting systems with similar functionality but distinct APIs.

Since there is a multitude of authentication mechanisms in use and many APIs implement proprietary variants of standard protocols, providing a single authentication mechanism for multiple systems is a key feature of Unified APIs and probably one of the largest time-savers for integration developers. However, features such as standardized pagination, filtering, and sorting are also essential to enable developers to retrieve data across different platforms efficiently.

​

Common data model

The Unified API standardizes models of data for each category of software and normalize data from each system into these standardized data schemas. It is the responsibility of the Unified API to decide what data is common across a given category, and how best to represent it in a normalized model. Thus, developers only need to implement a single code base to access data across many systems.

As an example, the currency of an account may be represented with the field ‘CurrencyCode’ in Xero and ‘currency’ in sevdesk, while the account model in Lexware Office does not have any corresponding field since Lexware Office only supports euro as currency. The Unified API provider would make a decision on how to represent currency across integrations, for example with a ‘currency’ field in the common data model and to always return ‘EUR’ in this specific field for Lexware Office. Thus, the Unified API does the hard lifting and the integration developer can rely on always receiving normalized and consistent data!