Sync data with weclapp
Unified. Reliable. Secure.
weclapp is a cloud ERP platform used by SMEs in Germany and the German-speaking market. It covers CRM, accounting, inventory, projects, and e-commerce connections. The API is REST-based and uses a tenant-specific subdomain URL with an AuthenticationToken header. API v2 is the current version and consolidates several previously separate endpoints, most notably merging customers, suppliers, contacts, and leads under a single /party endpoint.
Integrate weclapp alongside dozens of other accounting and ERP systems through Maesn Unified API.
Tenant-Specific Subdomain URL: No Central API, Each Customer Instance Has Its Own Base URL
Every weclapp customer has a unique subdomain URL in the format https://your-tenant.weclapp.com. There is no central API endpoint shared across all customers. For multi-tenant SaaS products, each customer's subdomain must be collected, stored, and used as the base URL for all their API requests. Maesn handles per-tenant URL management as part of its onboarding flow.
API v2 Consolidation: /party Replaces Separate Customer, Supplier, Contact, and Lead Endpoints
Die weclapp API v2 hat die zuvor getrennten Endpunkte /customer, /supplier, /contact und /lead zu einem einzigen Endpunkt /party zusammengeführt. Produkte, die auf v1 basieren oder separate Entitätsendpunkte erwarten, funktionieren nicht mehr oder geben leere Ergebnisse zurück, wenn sie nicht aktualisiert werden. Maesn normalisiert das v2-Party-Modell in sein gemeinsames Datenmodell und stellt Kunden, Lieferanten und Kontakte über einheitliche Endpunkte zur Verfügung.
User-Level API Token With Permission Scope: Token Access Matches User Role in weclapp
weclapp API tokens are generated per user and inherit that user's permissions within the weclapp account. A token from a user without access to accounting functions will return authorization errors on accounting endpoints. For multi-tenant SaaS products, this means the connecting user must have the correct role in their weclapp account. Maesn's onboarding documentation communicates the required permissions clearly.
"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
Trusted by winning dev teams
Learn more about weclapp 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 weclapp API With Maesn
Secure & Compliant
We have a strong relationship to weclapp. 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.
weclapp Sandbox
We provide you with everything you need, so you can focus on what counts.
weclapp is a cloud ERP platform for SMEs, primarily used in Germany and the broader German-speaking market. It covers CRM, accounting, inventory, project management, and e-commerce connections. The current API version is v2.
The main challenges are managing per-tenant subdomain URLs with no central API endpoint, adapting to the v2 consolidation where customers, suppliers, contacts, and leads are unified under the /party endpoint, ensuring the connecting user has the correct permissions for the required API methods, and handling rate limiting (HTTP 429) under high request volumes.
weclapp API v2 introduced stricter field validation and consolidated several previously separate endpoints. The most significant change is that /customer, /supplier, /contact, and /lead were merged into a single /party endpoint. Other endpoints were also renamed or restructured. Products built against v1 need to be updated to use v2 endpoints.
weclapp uses a multi-tenant architecture where each customer's data is hosted under their own subdomain. There is no shared central API domain that routes to all instances. For SaaS products serving multiple weclapp customers, this means the base URL is a customer-specific configuration value rather than a fixed constant.
A direct weclapp integration requires managing per-tenant subdomain URLs, adapting to the v2 /party consolidation, verifying the connecting user's permissions, and handling rate limiting. Maesn handles all of this through a single unified API.
Frequently Asked Questions About weclapp Integration
