Abacus API Integration Guide: REST API, AbaConnect WebServices & Unified Access
- Dr. Themo Voswinckel ⎪Co-Founder
- 5 days ago
- 6 min read
Updated: 1 day ago
This article serves as the starting point for building robust integrations to Abacus API and the variety of related Abacus modules.
We’ll also compare how Maesn Unified API simplifies the integration and eliminates the peculiarities for Abacus API that needs to be considered, if you develop without Maesn. This includes the complexity of the different integration options via REST API and AbaConnect WebServices. Find detailed technical capabilities in our developer documentation for Abacus and AbaConnect Webservices.
Key Takeaways of Abacus API Integration
Abacus offers two different options for integrations: via REST API or via AbaConnect WebServices (SOAP API)
Some Abacus modules (as AbaBau) and the related objects are only available with the AbaConnect webservices
Maesn supports both integration options to support all modules and industry specific variants of Abacus, incl. authentication etc.
One integration with Maesn unlocks Abacus API Integration and dozens of other ERP systems via one Unified API
Abacus is one of the most established and widely used SME ERP systems in Switzerland
Abacus is playing a central role in the digital infrastructure of SMEs, fiduciaries, construction companies, service organizations, and manufacturing firms. Although Abacus is most dominant in Switzerland, it is also used in parts of Liechtenstein, Austria and southern Germany.
Abacus has grown into a comprehensive business platform covering finance, payroll, HR, procurement, project management, time tracking, CRM, inventory and industry-specific modules such as AbaBau for construction. Its broad functional scope and deep configurability make it a popular system for Swiss mid-sized businesses that require both flexibility and strong local compliance. Many installations are operated either on-premise or by regional hosting providers, which has shaped Abacus into a highly modular, decentralized ecosystem with instance-specific configurations.
This combination of functional depth, local market relevance, and long-standing adoption across thousands of companies makes Abacus a key ERP to integrate with, but also one of the more complex ones due to its multi-layered API landscape, version differences, and module-driven architecture.
Abacus offers REST API and AbaConnect Webservice for integrations
Abacus offer three ways to integrate: REST API, ODBC/JDBC or AbaConnect webservice (SOAP API). For clean and object-based integrations we recommend (and only support) the integration via REST API and AbaConnect WebService. We strongly recommend, for a smooth authentication journey for your customers, to rely on only one approach. That's why we treat them as two separate target systems (Abacus vs. AbaConnect) in our API, but support both with Maesn.
The Abacus REST API covers many basic endpoints
Although many objects are supported by the REST API, certain Abacus modules as AbaBau require objects that are available via the REST API. For example - if you're using the Ababau extension, you will not be able to extract/import the sales orders/bill of materials via the REST API. In case it is the relevant system for your customer, you must build the integration with AbaConnect.
The AbaConnect Webservice is SOAP-based and needs to be activated in Abacus
The SOAP API has limitations, and it is a bit tricky to implement the first time. One important prerequisite: The AbaConnect WebServices needs to be available in the Abacus instance and accessible for the user. Some important aspects for the integration:
Reauthentication in AbaConnect is required every 30 minutes
After the user is authenticated, the token will expire after 30 minutes, which is a very short lived token. Especially as you don't get a 'refresh token' of any kind in the authentication flow. You simply have to do the login api call again.
If you integrate via Maesn, that's handled in our backend. If the token is inactive, we will refresh it in our backend, so that your token will always be active. No need to worry about re-authenticating.
Dedicated user for integration in Abacus needed
A dedicated user account in Abacus is required specifically for integrations. This is necessary because if an integration is configured using a user account that is actively used by a person, the session may become invalid, which would require manual re-authentication. Using a dedicated integration user ensures stable, uninterrupted operation of the integration.
Abacus AbaConnect endpoints are asynchronous
This means, that a flow for asynchronous requests needs to be implemented. If the request is not finished, you will receive a request ID and must wait until isFinished=true (usually 1–3 seconds depending on if it's a post request or get request).
With Maesn, you benefit from our Asynchronous Task Feature, which ensures reliable handling of long-running requests. Once a request is completed, you receive the response directly. If it is still in progress, a taskId is returned instead. You can then call the /asyncTask/{taskId} endpoint to check the current status of the request (in progress or finished). As soon as the task is completed, the endpoint will also return the final response.
AbaConnect offers a versatile documentation
AbaConnect offers a very extensive documentation landscape. Abacus provides information across multiple sources, including online info pages, PDF documents, and WSDL/XSD files. While comprehensive, this fragmentation makes it time-consuming and cumbersome to navigate and consolidate all relevant information for integration purposes.
Abacus REST API and AbaConnect SOAP API unified in Maesn
We have built a layer on top of both interfaces with Maesn. Working with us, you'll be working with our common data model that applies for all systems that we support with Maesn.
Unique URL for each Abacus instance and Mandant handling
Unlike most APIs, Abacus doesn’t have a universal base URL. Instead, each Abacus instance is set up with its own unique URL. This is because Abacus can either be installed locally by the customer or hosted online by a provider. Each server where Abacus is installed has its own base URL, and in some cases, providers even assign different URLs to different customer Mandants. This creates a real challenge when building integrations, because there’s no single host or fixed endpoint. You have to know and track the base URL for each customer, which becomes messy and hard to manage.
Request of base URL as part of authentication flow with Maesn
To solve this, we’ve made it possible to send the user’s base URL as a query parameter during authentication. Once sent, it gets saved and tied to the authenticated user. This means you don’t need to worry about managing the base URL anymore, and saving it for each customer. You can just focus on building one integration to Maesn. to get access to dozens of ERP systems and we’ll take care of the rest.
Mandants are the Environments in Abacus - supported via Maesn
Abacus supports having multiple Mandants (in other ERP often called Environments or Companies) within on Abacus instance. You can send them as query parameters or use our Interactive Authentication Flow, where your customer simply select the mandant they want to work with from a list of mandants.
No public sandbox available for Abacus API Integration
To receive a sandbox for Manual process with the API team of Abacus. They setup a user for testing purposes. All data resets every day. Together with our partner Abacus we ensure to provide you with your Abacus sandbox instance. Get a sandbox: Manual process with the API team of Abacus. They setup a user for testing purposes. All data resets every day. Together with our partner Abacus we ensure to provide you with your Abacus sandbox instance.
Required Setup by the User for Abacus API Integration
To access any entities via the Abacus API, except for Abacus Toolkit entities, the corresponding Abacus application must be properly configured. In addition, the AbaConnect option for each relevant application needs to be explicitly enabled.
All required prerequisites and the detailed setup steps that must be completed in advance are described in our documentation: Abacus and AbaConnect.
Annual Abacus Versions and Corresponding APIs
Abacus releases a new major version every year, and each version comes with its own set of REST APIs. As a result, API capabilities and supported objects can vary significantly between versions.
The table available on Abacus API Hub provides an overview of the supported objects for each Abacus version. This also makes it possible to identify which objects are supported by the Maesn Unified API for each version (see the overview in Abacus and AbaConnect).
Requirements to Get Listed in the Abacus Partner Marketplace
Abacus operates a partner marketplace that requires a manual and individual application process. Getting listed involves a formal qualification procedure defined by Abacus. Maesn supports you throughout this process by guiding you through the requirements, preparing the necessary materials, and assisting you during the Abacus qualification and approval steps.
Abacus API Integration and All Other Relevant Financial Systems - via Maesn Unified API
Integrating with Abacus ERP offers powerful capabilities to your product - but as described, it also comes with a few things to consider when integrating directly to Abacus.
That’s where Maesn changes the game. We provide ready-to-use REST API, clean documentation, normalized data model and much more - so you can focus on your product and deliver additional value to your users instead of building infrastructure. Maesn acts as the abstraction layer on top of Abacus (and all the other Financial/ERP systems your customers request), smoothing over the differences and peculiarities so you can focus on developing your own solution! With one integration to Maesn, you can build a more streamlined and resilient integration without reinventing the wheel for each provider. As APIs continue to evolve, we ensure you remain insulated from changes or odd behaviors in any single API.
