JTL-WAWI API (OnPrem) (1.1)
JTL-Wawi-Version: 1.11.0.0
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://wawi-api.jtl-software.com/?#tag/appRegistration. This information has to include the following:
- AppId
- DisplayName
- Description
- Version
- ProviderName
- ProviderWebsite
- MandatoryApiScopes
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.
To make a successful API request, it is essential to include the correct authentication data in the request header. Upper case and lower case is ignored. The header should contain the following information:
- X-AppID: This is the name of your application, in this case "MyApp/1.0.0". It is used to identify your application.
- X-AppVersion: This is where the version number of your application is entered, in this case "1.0.0".
- X-RunAs: Here, a JTL-Wawi user can be specified to perform an API call on their behalf (more details in the documentation).
- X-ChallengeCode: You can enter any custom value here. The X-ChallengeCode is used during app registration and must be the same for all registration requests. The maximum length is 30 characters.
- Authorization: The API key. Example: "Wawi 00000000-0000-00000-0000-000000000000"
https://developer.jtl-software.com/_mock/products/erpapi/openapi/
http://127.0.0.1:61894/api/eazybusiness/
This is the name of your application, e.g. "MyApp/1.0.0". It is used to identify your application.
This is where the version number of your application is entered, e.g. "1.0.0".
The User-Id (int or uuid) on whose behalf the request is executed. Requires scope 'Application.RunAs'.
The workflow event.
- Mock server
https://developer.jtl-software.com/_mock/products/erpapi/openapi/v1/items/{itemId}/workflowEvents
- Local OnPremise Environment
http://127.0.0.1:61894/api/eazybusiness/v1/items/{itemId}/workflowEvents
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X POST \
'https://developer.jtl-software.com/_mock/products/erpapi/openapi/v1/items/{itemId}/workflowEvents' \
-H 'Authorization: YOUR_API_KEY_HERE' \
-H 'Content-Type: application/json' \
-H 'X-SessionId: 497f6eca-6276-4993-bfeb-53cbbbba6f08' \
-H 'x-appid: string' \
-H 'x-appversion: string' \
-H 'x-runas: string' \
-d '{
"Id": 1
}'- Mock server
https://developer.jtl-software.com/_mock/products/erpapi/openapi/v1/items/customfields
- Local OnPremise Environment
http://127.0.0.1:61894/api/eazybusiness/v1/items/customfields
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
https://developer.jtl-software.com/_mock/products/erpapi/openapi/v1/items/customfields \
-H 'Authorization: YOUR_API_KEY_HERE' \
-H 'X-SessionId: 497f6eca-6276-4993-bfeb-53cbbbba6f08' \
-H 'x-appid: string' \
-H 'x-appversion: string' \
-H 'x-runas: string'The requested custom fields for items.
0 = None, 1 = Integer, 2 = Decimal, 3 = Text, 4 = Checkbox, 5 = List, 6 = Url, 7 = Email, 8 = PhoneNumber, 9 = CountryIso, 10 = Price, 11 = Date, 12 = ShortText
The possible values, when the custom field is a list.
[ { "Attribut": { … }, "CustomFieldId": 0, "GroupName": "Example Group", "Name": "Technical Data", "Type": 0, "PossibleValues": "" } ]
- Mock server
https://developer.jtl-software.com/_mock/products/erpapi/openapi/v1/items/imagedata/{imageId}
- Local OnPremise Environment
http://127.0.0.1:61894/api/eazybusiness/v1/items/imagedata/{imageId}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://developer.jtl-software.com/_mock/products/erpapi/openapi/v1/items/imagedata/{imageId}' \
-H 'Authorization: YOUR_API_KEY_HERE' \
-H 'X-SessionId: 497f6eca-6276-4993-bfeb-53cbbbba6f08' \
-H 'x-appid: string' \
-H 'x-appversion: string' \
-H 'x-runas: string'