Skip to main content
Track platform updates, API changes, SDK releases, deprecations, and developer-facing fixes across the JTL Platform. The most recent updates appear first.
BadgeMeaning
A change that requires action to keep your integration working.
A new endpoint, feature, or capability.
Existing behaviour has changed.
A feature is scheduled for removal in a future release.
A previously deprecated feature has been removed.
A bug has been resolved.
A security-related update or hardening change.
Version tags identify the API version an entry applies to. Entries without a version tag affect the broader platform, SDKs, Partner Portal, documentation, or tooling.

​
2026-04-15 · App Manifest 2.0 is now the default

Cloud Apps Manifest Partner Portal The App Manifest format is moving from 1.0 to 2.0. Manifest 2.0 separates runtime configuration from listing and marketing metadata. Technical fields remain in the manifest file, while marketing content such as app names, descriptions, icons, and screenshots move into a dedicated Listing system managed through the Partner Portal.

​
Added

  • New top-level fields:
    • manifest section with technicalName and lifecycle.configurationUrl
    • listing section with marketing metadata
These are now managed through the Partner Portal UI.
Manifest 1.0 is not backward compatible after the migration cutover completes.

​
Action Required

  • Update manifest file to version 2.0
  • Move marketing metadata into the listing section

​
2026-03-05 · Cloud API v2.0 is now the default

v2.0 API Cloud API GraphQL OnPremise API API Reference now defaults to v2.0. Earlier versions (v1.0 through v1.4) remain available through the version selector, but new integrations should target v2.0. Cloud API continues to use URL-path versioning. Example: 
https://api.jtl-cloud.com/erp/v2/graphql
OnPremise APIs continue to use header-based versioning with: 
api-version: 2.0