Trusted by winning dev teams
Sync data with Twinfield
Unified. Reliable. Secure.
Twinfield is a cloud accounting platform used by accounting firms and SMEs across the Netherlands, Belgium, and the UK. It is part of the Wolters Kluwer group and is particularly popular with accounting practices managing multiple client entities. The API uses OAuth 2.0 for authentication and SOAP/XML as its primary data exchange protocol, with all requests routed through a cluster-specific base URL that must be resolved after authentication.
Integrate Twinfield alongside dozens of other accounting and ERP systems through Maesn Unified API.
SOAP/XML Protocol: Not REST, Requires XML Envelope Construction on Every Request
Unlike most modern accounting APIs, Twinfield's primary API is SOAP-based and requires well-formed XML envelopes for all data operations. Every request must include an AccessToken and a CompanyCode in a SOAP header. For development teams accustomed to REST and JSON, SOAP adds significant implementation overhead. Maesn exposes Twinfield through a standard REST interface, handling XML construction and parsing internally.
Cluster-Specific Base URL: Must Be Resolved Post-Authentication Before Any Data Request
After OAuth authentication, Twinfield returns a cluster URL that determines which server hosts the authenticated user's data. All subsequent API requests must use this cluster-specific base URL, for example api.eu01.twinfield.com. Using the wrong cluster URL causes all requests to fail silently. Maesn resolves the cluster URL during onboarding and routes all requests correctly per tenant.
CompanyCode Required Per Request: Multi-Entity Context Must Be Managed Across All Calls
Every Twinfield request must include a CompanyCode in the SOAP header identifying the specific company being accessed. Accounting firms managing many client entities must store and switch between company codes per request. Maesn stores the CompanyCode per tenant and injects it into every request automatically.
"Adding Qonto to our existing integrations was a piece of cake with Maesn. It is a game changer for our customers with all the integration cababilites!"
Juri Preis
CEO @ Smarta
Learn more about Twinfield API Integration
The Maesn difference
Built faster and sell more with Maesn
Stop keeping your engineers busy with building one integration after the other. Focus on your core value: Your product.
Focus on your core product
Engineering focus
Enable your sales team to have what your leads want. Launch a portfolio of integrations in days, not quarters. Accelerate your sales.
Stop losing deals due to integrations
Sales enablement
Integrations reduce churn - dramatically. Increase your customer satisfaction with end-to-end integration to all relevant systems.
Tie your customers for ever
Higher customer retention
Integrate with
Maesn API
Production
approval
Integration
App
Why companies choose Maesn
3 Reasons Why It Is Better To Integrate Twinfield API With Maesn
Secure & Compliant
We have a strong relationship to Twinfield. This ensures that the Maesn API is always up-to-date and any maintenance is covered on our end.
Common Data Model
We provide a clean, unified data model that abstracts away system-specific quirks, so teams can build reliable integrations without dealing with ERP-specific complexity or workaround-heavy implementations.
Twinfield Sandbox
We provide you with everything you need, so you can focus on what counts.
Twinfield is a cloud accounting platform by Wolters Kluwer, used by accounting firms and SMEs primarily in the Netherlands, Belgium, and the UK. It is particularly popular with accounting practices managing multiple client entities. The API uses OAuth 2.0 authentication and a SOAP/XML protocol.
The main challenges are implementing SOAP/XML instead of standard REST, resolving the cluster-specific base URL post-authentication before making any data requests, managing the CompanyCode context per request for multi-entity accounting firms, and constructing valid SOAP envelopes with the correct access token and headers.
Twinfield's API architecture predates the widespread adoption of REST and uses SOAP/XML as its primary protocol. This is common in enterprise accounting systems of Twinfield's generation. SOAP requires constructing XML envelopes for every request and parsing XML responses, which adds significant implementation overhead compared to REST/JSON APIs.
After OAuth authentication, Twinfield returns a twf.clusterUrl value that specifies which server infrastructure hosts the authenticated user's data. All subsequent API requests must target this cluster URL. Using the default or a hardcoded URL instead of the cluster URL causes all requests to fail, since the data may be hosted on a different cluster.
A direct Twinfield integration requires implementing SOAP/XML, resolving and storing the cluster URL post-authentication, managing CompanyCode context per request, and maintaining XML envelope construction for all operations. Maesn handles all of this through a standard REST interface.
Frequently Asked Questions About Twinfield Integration
