Skip to main content
The JTL ERP API lets you read and modify JTL-Wawi data: orders, products, customers, stock, and more. Every merchant runs the same Wawi API on their own Wawi instance. What differs is how your integration reaches it.
OptionBase URLWhere your integration runs
OnPremisehttp://127.0.0.1:64110/api/eazybusiness/On the merchant’s machine or their local network
Cloudhttps://api.jtl-cloud.com/erp/Anywhere. The request is forwarded to the merchant’s Wawi
The Cloud option is available when a merchant has connected their Wawi to JTL Cloud. The public endpoint forwards requests to their Wawi, letting your integration run off the merchant’s premises without access to their network. Both variants expose the same API surface through REST and GraphQL. They differ in:
  • where your integration can be deployed
  • how authentication works
  • a small set of variant-specific capabilities

​
Authentication

The authentication flow depends on the variant. Cloud uses OAuth 2.0 client credentials; OnPremise uses a two-step registration flow.
1

Register in the Partner Portal

Register your app in the JTL Partner Portal to receive a clientId and clientSecret.
2

Request an access token

Send a POST request to https://auth.jtl-cloud.com/oauth2/token with Basic auth (base64 clientId:clientSecret) and body grant_type=client_credentials. The response returns a JWT access token valid for one hour.
3

Call the API

Include the JWT as Authorization: Bearer <JWT> on every request, along with the merchant’s X-Tenant-ID.
See the OAuth 2.0 flow for more details.

​
Required HTTP Headers

Every API request must include the headers below:
HeaderDescription
AuthorizationBearer <JWT> obtained from the OAuth 2.0 token endpoint
X-Tenant-IDThe merchant’s tenant ID
See the versioning guide for more details on API versioning.

​
Next Steps

Available APIs

A guided tour of the REST API domains and what each one does.

Authentication

Auth flows across Cloud Apps, OnPremise, and SCX.

API Reference

Browse all REST API endpoints with request/response schemas.