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. In the API Server's admin UI create an App and copy the generated key. JTL issues it base64-encoded; use it exactly as given.
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: Bearer <key> and X-AppId.

Set JTL_WAWI_APP_ID to the App id shown next to the key. JTL routes and rate-limits per app.

Pagination is header-driven. JTL's list endpoints take $top and $skip and return the total in an X-Total-Count response header. 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. Availability questions need the second one — the article master's stock field is a cached roll-up and can lag.

Unverified. The paths and field names below follow the vendor's published documentation and have not been exercised against a live tenant. 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.