JTL-Wawi

JTL-Wawi is on-premises Windows software and does not speak HTTP on its own. The REST API is served by the separate JTL API Server (sometimes called the Wawi API / JTL-Wawi API), which you install alongside the Wawi database.

1. Install the JTL API Server on the machine that reaches your JTL-Wawi MSSQL database, and start its service.
2. Register an app: in JTL-Wawi open Admin → App registration and start the registration, then send POST /api/eazybusiness/authentication with the app's details (AppId, DisplayName, Description, Version, ProviderName, ProviderWebsite, MandatoryApiScopes) and an x-challengecode header. Approve the request in Wawi and call GET /api/eazybusiness/authentication/{registrationId} with the same challenge code: the response holds the permanent ApiKey. It is shown only once.
3. Set JTL_WAWI_URL to the API server's root (e.g. https://wawi.example.com:5883, no trailing slash) and JTL_WAWI_API_KEY to the key. The adapter sends Authorization: Wawi <key>.

Set JTL_WAWI_APP_ID and JTL_WAWI_APP_VERSION to the AppId (e.g. MyApp/1.0.0) and Version used at registration. They travel as the X-AppId and X-AppVersion headers on every call.

Pagination is page-based. List endpoints take pageNumber (from 1) and pageSize, and the response body carries TotalItems, TotalPages and HasNextPage. Ask for a page, look at the total, ask for the next — do not loop blindly.

Item vs stock. jtl_wawi_list_items returns the article master (name, SKU, prices); jtl_wawi_get_item_stock returns the per-warehouse quantities from /stocks. Availability questions need the second one.

Orders and shipments. jtl_wawi_list_sales_orders filters by order number, customer or date (no free-text search). An order's lines come from jtl_wawi_list_sales_order_line_items. Shipments are delivery notes (/deliveryNotes); their packages carry the tracking id and URL.

Checked against JTL's published OpenAPI (ERP API 1.x), not a live system. Paths, parameters and the Wawi auth scheme follow developer.jtl-software.com; JTL's 2.0 API changes many endpoints, and this adapter stays on the /v1 routes. Treat a 404 as a docs-versus-reality gap and check the developer portal before concluding that the credential is wrong. A correction from anyone running this against a real system is genuinely welcome.

Self-hosted, which is the thing to plan for.

• On AnythingMCP Cloud the instance must be reachable from the public internet on a real hostname with a valid TLS certificate. A self-signed certificate will fail: the connector offers no trust-anything switch.
• On an internal host (wawi.intern, 10.0.0.x), self-host AnythingMCP on the same network and add that host to SSRF_ALLOWED_HOSTS, or the outbound guard refuses the call before it is made.