> ## Documentation Index
> Fetch the complete documentation index at: https://developer.jtl-software.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Support

> Developer resources, support channels, and community spaces for building on the JTL Cloud Platform.

Support channels and community spaces for developers building on the JTL Cloud Platform.

## Quick Links

<CardGroup cols={2}>
  <Card title="Partner Portal" icon="building" href="https://partner.jtl-cloud.com">
    Register apps, manage integrations, and access partner resources.
  </Card>

  <Card title="API Reference" icon="code" href="/api-reference">
    Browse the full API reference for the current stable version.
  </Card>

  <Card title="Guides" icon="book" href="/guides">
    Implementation guides for authentication, webhooks, Cloud Apps, and more.
  </Card>

  <Card title="Error Handling" icon="triangle-alert" href="/guides/essentials/common-patterns/error-handling">
    Troubleshoot API errors, validation failures, and retry behaviour.
  </Card>
</CardGroup>

## Support Channels

Different channels are best suited for different kinds of questions. Use the one that matches the type of help you need.

### Microsoft Teams

The public JTL Cloud Teams workspace is the fastest place for:

* Quick implementation questions
* Architecture discussions
* Integration feedback
* Community troubleshooting

Both JTL staff and other developers participate in discussions.

<CardGroup cols={2}>
  <Card title="Join the Teams Community" icon="microsoft" href="https://teams.microsoft.com/l/channel/19%3AEIyOrcDs8titIBBfmjESpDuipq2wikfaxT_sFe2xYv81%40thread.tacv2/Allgemein?groupId=85e2e4a3-e4cb-499f-bda1-a2f95fb346bb&tenantId=b27e7bb8-fdc1-49ef-91c0-b251c2f24c72">
    Get help with integrations, platform issues, and partner questions
  </Card>
</CardGroup>

Available to anyone with a Microsoft account.

***

### Email Support

Best for:

* Account-specific questions
* Production issues
* Private discussions
* Cases where you want a written support thread

<CardGroup cols={2}>
  <Card title="cloud@jtl-software.com" icon="mail" href="mailto:cloud@jtl-software.com">
    Contact the JTL Cloud team
  </Card>
</CardGroup>

General questions and feedback can always be sent to the Cloud team by email.

***

### Partner Ticket System

Existing JTL partners with a Customer Center Account can create support tickets directly through the JTL support system.

Best for:

* Escalated support requests
* Partner-specific issues
* Operational problems requiring formal tracking
* Longer-running investigations

<CardGroup cols={2}>
  <Card title="Create a Support Ticket" icon="ticket" href="https://kundencenter.jtl-software.de/support/createticket">
    Open the JTL support ticket system
  </Card>
</CardGroup>

Available to existing partners only.

The ticket system is currently available in German.

***

### GitHub

JTL's GitHub organisation hosts:

* SDKs
* Sample apps
* Starter templates
* Open-source tooling

Use GitHub issues to:

* report bugs
* request improvements
* contribute fixes or feedback for JTL-maintained repositories

<CardGroup cols={2}>
  <Card title="JTL on GitHub" icon="github" href="https://github.com/jtl-software">
    Browse repositories and open issues
  </Card>
</CardGroup>

Open to anyone with a GitHub account.

For platform-specific issues unrelated to a repository, use Teams, email, or the support ticket system instead.

***

### Community Forum

The JTL community forum is the largest public discussion space for the ecosystem, including:

* Cloud Platform
* JTL-Wawi
* JTL-Shop
* OnPremise APIs
* Shipping integrations

Searching existing threads first is recommended; many common integration questions already have answers.

<CardGroup cols={2}>
  <Card title="forum.jtl-software.de" icon="message-circle" href="https://forum.jtl-software.de">
    Browse discussions and ask questions
  </Card>
</CardGroup>

Replies may come from community members, partners, or JTL staff.

## Before Contacting Support

Including the right details in your first message usually leads to faster resolutions.

### For Technical Questions

Include:

* Your `appId`
* Whether you're working in development or production
* The API endpoint involved, including method and path
* The full error response and status code
* A minimal reproduction case
* What you've already tried

### For Account or Access Questions

Include:

* Your partner account email
* Company name
* The app or tenant involved
* What you expected to happen
* What happened instead

## Additional Resources

<CardGroup cols={2}>
  <Card title="Changelog" icon="history" href="/help/changelog">
    Track platform updates, improvements, and breaking changes.
  </Card>

  <Card title="Quickstart Guides" icon="rocket" href="/get-started/quick-start/from-template">
    Build and deploy your first Cloud App.
  </Card>

  <Card title="Webhooks & Events" icon="bell" href="/guides/essentials/common-patterns/webhooks">
    Understand AppBridge events, the setup handshake, and SCX polling.
  </Card>

  <Card title="Authentication" icon="shield-check" href="/guides/essentials/authentication/oauth2-flow">
    Learn how authentication and app installation work on the platform.
  </Card>
</CardGroup>