Platform Overview - JTL Developer Documentation

The JTL Cloud platform is the developer surface for JTL Software’s ERP and commerce suite. It exposes core merchant systems (products, inventory, orders, and marketplace connectors) through APIs, a messaging layer, a manifest-based app model, and an App Store. For hands-on setup, see Get Started. For implementation detail on a specific app type, see Cloud Apps Architecture.

Platform Capabilities

Capability	What you get	Reference
Integration surfaces	Render inside ERP Cloud, launch from a JTL Hub tile, or as a panel in ERP Cloud	Integration Surfaces
Data access	Read and write merchant data (orders, products, customers, invoices) over REST and GraphQL	Using Platform APIs
Authentication	OAuth 2.0 client credentials for your backend, short-lived session tokens for your frontend	Security & Compliance
AppBridge	Two-way messaging between your app and ERP Cloud for exchanging data and triggering events,	App Shell & UI Integration
Design system	Platform UI, a React component library matching the JTL look and feel	App Shell & UI Integration
Distribution	Register in the Partner Portal, publish to the App Store, install via JTL Hub	Get Started
Monetization	Configure pricing plans for your app. JTL handles invoicing, billing, and payouts on your behalf. (Coming soon.)	—
Marketplace sync	Connect a marketplace channel via SCX, a separate platform that integrates with JTL-Wawi	Marketplace Channels

Integration Surfaces

A Cloud App declares its integration surfaces in the app.json. Three types are available, and a single app can use any combination.

Type	Where it renders	Communication	Typical use
Hub-Link	Card in JTL-Cloud Hub; clicking redirects the merchant to your URL	None (redirect only)	Entry points to external tools and dashboards
ERP-iFrame	Main content area of ERP Cloud, reached from the ERP sidebar	AppBridge messaging	Rich interactive UI inside the merchant’s ERP workspace
Panel	Sidebar panel on specific ERP Cloud views	AppBridge messaging; context-aware	Panels that react to the current customer, order, or product

All three require app registration in the Partner Portal and OAuth 2.0 client credentials for backend API access. The UI-bearing types (ERP-iFrame and Panel) render as iframes and have full AppBridge access; the difference between them is placement. Hub-Link is a redirect, not an iframe. See Cloud Apps: Architecture for more details.

Developer Lifecycle

Building on JTL follows a consistent lifecycle, regardless of the integration surface. You register your app in the Partner Portal and receive client credentials. You build and test against a sandbox tenant inside the ERP shell. When ready, you create an App Store listing and attach a pricing plan. Approved apps become available for merchants to buy and install. Each step is covered in Get Started.

What’s Next

Get Started

Set up accounts and ship your first app.

Cloud Apps Architecture

How a Cloud App is structured and communicates with JTL.

Essentials

Auth, errors, pagination, webhooks, versioning.

API Reference

OpenAPI reference for the Cloud API.

​Platform Capabilities

​Integration Surfaces

​Developer Lifecycle

​What’s Next