JTL Custom API Integration

Custom REST interfaces for DATEV, BI, ERP or specialized marketplaces, from 990 €.

JTL-Wawi is not an isolated system, it is the central hub of your e-commerce operation. For this hub to reach its full value, it needs to talk to the systems you use every day: accounting software, shipping platforms, BI tools, CRM systems, marketplaces and fulfillment providers. TwoPixels builds and operates these connections as an official JTL Service Partner with its own MCP server stack.

JTL Service Partner with Its Own API Stack

TwoPixels operates its own JTL MCP server (apps-core, port 3100), acting as an API adapter between the JTL-Wawi MSSQL database and any third-party system. This adapter is not a generic tool, it is built specifically for the requirements of our clients: tenant isolation, structured error handling, complete request logging and a unified JSON response format.

The advantage of this approach: new interfaces are never implemented as direct connections to the JTL database (which can cause performance problems and security risks), but as cleanly defined API endpoints that can be tested, versioned and monitored.

Dedicated JTL MCP server (Node.js, apps-core:3100)
API endpoints for orders, products, customers, stock and shipping
Tenant isolation: each client has dedicated endpoints and access control
JSON-based response format for easy downstream processing
Request logging and error monitoring for every API call

Which Third-Party Systems Can Be Integrated?

TwoPixels has implemented API integrations for a range of system categories. The most common requests involve accounting (DATEV, Lexoffice, Sevdesk), shipping platforms (Shipcloud, Sendcloud, DHL business customer portal), business intelligence tools (Metabase, Grafana, Google Looker Studio) and marketplaces (Amazon, eBay, Otto via JTL-Ameise or a direct API integration).

In principle, any software with a REST API can be integrated. What matters is the data model analysis: which fields from JTL need to map to which fields in the target system, how conflicts are handled and which side is the master. We carry out this planning before every implementation.

Accounting: DATEV export, Lexoffice, Sevdesk, Billomat
Shipping: DHL, DPD, UPS, Hermes, Shipcloud, Sendcloud
BI & reporting: Metabase, Grafana, Google Looker Studio, Excel export
Marketplaces: Amazon MWS, eBay, Otto (via JTL-Ameise and direct)
CRM: HubSpot, Pipedrive, custom CRM solutions via webhook

n8n Automations for JTL Workflows

TwoPixels operates its own n8n instance for workflow automations that use JTL data as a source or a target. Typical use cases from our live operations: automatic blog posts generated from new JTL products (content enriched with AI and published directly to Shopify or WordPress), supplier alerts when stock falls below minimum levels, automatic inventory reports by email and webhook notifications for critical order status changes.

These automations run reliably on our n8n instance on apps-core and are fully multi-tenant. For new clients, the corresponding workflows can be configured and activated within a few days, without you needing any technical knowledge yourself.

Blog automation: new JTL product → AI enrichment → Shopify/WordPress post
Stock alert: inventory < threshold → email/Slack to purchasing
Inventory report: daily/weekly overview by email
Webhook trigger: order status changes → any action
Supplier API: automatic purchase order at minimum stock

Custom Integrations: From Requirement to Live Operation

Every custom integration at TwoPixels follows the same process: requirement analysis, data model mapping, implementation in a test environment, client sign-off, go-live with monitoring activated. No surprises after go-live, no integration without error handling.

Typical project timelines: simple export interfaces (e.g. JTL to CSV for accounting) in 1 to 3 working days. Bidirectional real-time synchronization with conflict handling in 2 to 4 weeks. Complex multi-system integrations based on an individual effort estimate.

Structured project flow: analysis → implementation → sign-off → go-live
Test environment before every go-live
Complete error handling in every interface
Monitoring and alerting from day one in production
Documentation of every implemented endpoint

FAQ, JTL API & Custom Integration

Does TwoPixels access the JTL-Wawi database directly?

Yes, through a controlled MSSQL connection, exclusively via defined adapters, never directly through ad hoc SQL from third-party systems. This protects database performance and data integrity.

Is the JTL REST API available for all Wawi versions?

The JTL-Wawi REST API is available from version 1.6 onward. For older versions we work with alternative access methods through a controlled adapter. We always recommend updating to a current version.

Can existing interfaces be taken over and further developed?

Yes. We analyze the existing integration code and documentation and then carry out a structured handover. In many cases we can significantly improve stability and performance along the way.

How are API credentials managed securely?

All credentials (API keys, MSSQL credentials) are managed in an encrypted secrets store. No plaintext credentials in configuration files or scripts.

Does TwoPixels also support webhook-based integrations?

Yes. We process JTL-Shopify webhooks through the Hub API. For other systems we implement the corresponding webhook receivers.

All JTL Services at a Glance

Request a Consultation Now

Speak directly with Christopher Schütz, Managing Director of TwoPixels GmbH and official contact as JTL Service Partner Silver.

Request a Consultation +49 1556 7039821

TwoPixels GmbH · Nadorster Straße 26 · 26419 Schortens · info@webagentur-twopixels.de

Get Free Consultation