LogisticsWMS API & Webhooks | LogisticsWMS Help

What it does

Lets external systems (your ERP, custom e-commerce, BI tools, etc.) talk to the WMS in two complementary ways: webhooks and REST API.

🔔 Webhooks (WMS → outside): the WMS automatically sends data to your systems when events happen (e.g. order created, stock updated). Configure the target URL per operation; outgoing requests are authenticated with user / password (HTTP Basic Auth).
🔑 API Clients (outside → WMS): external systems authenticate and call the WMS API directly to read or change data, under /api/external/v1/.
1. Create an API client — a Client ID and Client Secret are generated (the secret is shown only once).
2. Exchange the credentials for a JWT token valid for 1 hour: POST /api/external/v1/auth/token.
3. Use the token as Authorization: Bearer <token> in every subsequent call.
Each API client can be enabled / disabled, have its secret regenerated, or be deleted — without affecting the others.
All calls (webhooks and API clients) are logged in the Audit tab.
The complete technical docs are on Swagger.

Activate the plugin under Plugins → Other Integrations.
Under General Settings, enable the operations you want to expose and their defaults (e.g. whether products created via API always require batch / expiry date).
To notify external systems: configure the webhook URLs and outbound auth credentials under the Webhooks tab.
To allow calls into the WMS: create one or more API Clients under the corresponding tab and share the credentials with whoever will consume the API.

Store the Client Secret somewhere safe as soon as it's generated — it won't be shown again. If lost, regenerate it.
Webhook URLs must be publicly reachable for the WMS to deliver the notifications.
To get the initial client_id / client_secret, email [email protected] with the LogisticsWMS customer company name.

💡 Tip: inside the application, each plugin's configuration page has an Integration Guide button with the detailed technical walk-through.