URL https://developer.jtl-software.com/
JTL-Software-GmbH partner@jtl-software.com
Welcome to the JTL-WAWI technical API documentation. This guide is here to help developers understand how our REST API works and how it can be integrated into your existing systems. We'll delve into the details of authentication and data manipulation processes, providing clear examples along the way. Whether you're a developer or an IT professional, this documentation aims to give you a practical understanding, laying the groundwork for effectively using the JTL-WAWI API to enhance your processes.
You register your application with the API by sending a POST request with the required information and corresponding keys. You can find the exact request details at https://developer.jtl-software.com/products/erp/swagger/appregistration. This information has to include the following:
This data is crucial for identifying and registering your application with the API. The API uses it to generate a temporary authentication ID that allows your application to access the necessary resources. After successful validation of this information, you will receive the API key required for future authentication and API requests.
Before you can begin the registration process, you must open JTL-Wawi (new interface) and start the registration process under 'Admin->App registration'. Only at this point are you authorised to send the first API call. This step in JTL-Wawi ensures that your application is properly registered and has permission to use the API.
The API will send you an authentication ID in the form of a token. Once you have received this token and successfully completed the registration in JTL-Wawi, you will send another request to the API by including this authentication ID in the URL path.
After successful validation of this second request by the API and confirmation of the correct information, you will be provided with the actual API key. It is important to note that this API key will not be displayed again!
This API key will be used in the future to authenticate requests to the API. It is of utmost importance that you securely store the API key upon receipt, as it cannot be retrieved from any other location in the system.
This is the name of your application, in this case "MyApp/1.0.0". It is used to identify your application.
This is where the version number of your application is entered, in this case "1.0.0".
The User-Id as int or uuid to run the Request, a JTL-Wawi user can be specified to perform an API call on their behalf (more details in the documentation, Optional). To use the Header, you must have the needed Scope 'Application.RunAs'
curl -i -X DELETE \
'https://developer.jtl-software.com/_mock/products/erpapi/1.0-cloud/openapi/items/{itemId}/properties/{propertyValueId}' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'api-version: string' \
-H 'tenant-id: 497f6eca-6276-4993-bfeb-53cbbbba6f08' \
-H 'x-api-key: YOUR_API_KEY_HERE' \
-H 'x-appid: string' \
-H 'x-appversion: string' \
-H 'x-runas: string'This is the name of your application, in this case "MyApp/1.0.0". It is used to identify your application.
This is where the version number of your application is entered, in this case "1.0.0".
The User-Id as int or uuid to run the Request, a JTL-Wawi user can be specified to perform an API call on their behalf (more details in the documentation, Optional). To use the Header, you must have the needed Scope 'Application.RunAs'
curl -i -X GET \
'https://developer.jtl-software.com/_mock/products/erpapi/1.0-cloud/openapi/items/{itemId}/salesChannelPrices' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'api-version: string' \
-H 'tenant-id: 497f6eca-6276-4993-bfeb-53cbbbba6f08' \
-H 'x-api-key: YOUR_API_KEY_HERE' \
-H 'x-appid: string' \
-H 'x-appversion: string' \
-H 'x-runas: string'The requested item prices for sales channel.
The ID of the sales channel for this description. Only specific sales channels are allowed for this operation and are specified in the sales channel endpoint (GET).
Unique ID to identify a customer group. If CustomerGroupId is 0, the price will be the default value for all customer groups.
The quantity for the scale prices. This should be 0 or empty for the default price. If a FromQuantity is given, this price applies to the range from this quantity to the next specified FromQuantity. If no higher FromQuantity exists, then this price applies to all quantities from this point on.
The net sales price of the item. If you use NetPrice, you can't use ReduceStandardPriceByPercent too. Only one can be used.
Reduce the default sales price by a percentage. If you use NetPrice, you can't use ReduceStandardPriceByPercent too. Only one can be used.
[ { "ItemId": 1, "SalesChannelId": "1-1-1", "CustomerGroupId": 0, "FromQuantity": 0, "NetPrice": 126.04, "ReduceStandardPriceByPercent": 5 } ]
This is the name of your application, in this case "MyApp/1.0.0". It is used to identify your application.
This is where the version number of your application is entered, in this case "1.0.0".
The User-Id as int or uuid to run the Request, a JTL-Wawi user can be specified to perform an API call on their behalf (more details in the documentation, Optional). To use the Header, you must have the needed Scope 'Application.RunAs'
The sales channel price for an item to create.
The ID of the sales channel for this description. Only specific sales channels are allowed for this operation and are specified in the sales channel endpoint (GET).
Unique ID to identify a customer group. If CustomerGroupId is 0, the price will be the default value for all customer groups.
The quantity for the scale prices. This should be 0 or empty for the default price. If a FromQuantity is given, this price applies to the range from this quantity to the next specified FromQuantity. If no higher FromQuantity exists, then this price applies to all quantities from this point on.
The net sales price of the item. If you use NetPrice, you can't use ReduceStandardPriceByPercent too. Only one can be used.
curl -i -X POST \
'https://developer.jtl-software.com/_mock/products/erpapi/1.0-cloud/openapi/items/{itemId}/salesChannelPrices' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Content-Type: application/json' \
-H 'api-version: string' \
-H 'tenant-id: 497f6eca-6276-4993-bfeb-53cbbbba6f08' \
-H 'x-api-key: YOUR_API_KEY_HERE' \
-H 'x-appid: string' \
-H 'x-appversion: string' \
-H 'x-runas: string' \
-d '{
"SalesChannelId": "1-1-1",
"CustomerGroupId": 0,
"FromQuantity": 0,
"NetPrice": 126.04,
"ReduceStandardPriceByPercent": 5
}'The created item sales channel price.
The ID of the sales channel for this description. Only specific sales channels are allowed for this operation and are specified in the sales channel endpoint (GET).
Unique ID to identify a customer group. If CustomerGroupId is 0, the price will be the default value for all customer groups.
The quantity for the scale prices. This should be 0 or empty for the default price. If a FromQuantity is given, this price applies to the range from this quantity to the next specified FromQuantity. If no higher FromQuantity exists, then this price applies to all quantities from this point on.
The net sales price of the item. If you use NetPrice, you can't use ReduceStandardPriceByPercent too. Only one can be used.
{ "ItemId": 1, "SalesChannelId": "1-1-1", "CustomerGroupId": 0, "FromQuantity": 0, "NetPrice": 126.04, "ReduceStandardPriceByPercent": 5 }