Skip to main content
To help us answer your questions more quickly and accurately, we recommend that you provide additional information according to the submission guidelines when creating a ticket. Thank you very much for your feedback!

​
Self-Service Tools

If you encounter a problem during development, we recommend that you first read the relevant documentation or use the self-service tools to debug and locate the API you need to verify.
  • Server API Debugging Tool
  • Mini Program Development Debugging Tool
  • Micro App Frontend Debugging Tool

​
Technical Support

To provide you with better service quality and reduce your wait time, we recommend that you first try to resolve the issue with the self-service tools. If the issue persists, you can seek assistance through the following channels.
  1. Sign in to the Developer Console.
  2. Click Tabler in the lower-right corner.
  3. After clicking Tabler, you can enter your question in the input box to get help. If Tabler’s answer does not resolve your issue, click the Ticket Center below to submit a ticket.
  4. Submit the ticket. Note
    1. When submitting a service ticket, if you encounter an API call issue, provide the organization’s CorpID, the API documentation, the requestID, and other error details.
    2. After you submit a service ticket, the system automatically creates a group chat and assigns technical support (during business hours). Click Join Chat in the ticket list to join the group chat and communicate.
    3. To add other users to the group chat, do so yourself. Path: Ticket Chat Quick actions > Ticket Details > Add People button (only users within the same organization are supported).
    After entering the page, you can view and manage the issues you have submitted.

​
Ticket System Overview

The ticket system has upgraded its supporting service components to make it easier to record and follow up on issues, striving to bring developers a better service experience.
  • Ticket Center: Aggregates all tickets under the current organization, so the handling progress is clear at a glance.
  • Ticket Chat: During business hours (09:00 to 18:00 on business days), a dedicated DingTalk ticket chat is created within one hour for each submitted issue. Click the “Join Chat” button in the ticket list to communicate seamlessly with service staff through the group chat. This reduces communication steps and makes issue handling more efficient.
  • Service Timeline: Every issue handling process is recorded on a timeline, and all chat history during the process is saved, making the entire issue-handling lifecycle visible and transparent.
  • Confirmation and Evaluation: After the service staff provide a solution, a ticket-completion card is pushed to the group chat. If you confirm that the solution is effective, clickResolved**; if you do not accept the solution for now, clickUnresolved, and the service staff will continue to follow up until the issue is resolved.**
  • After the issue is resolved, you can rate the service provided by the service staff.

​
Notes

To help us quickly locate and troubleshoot the issue, we recommend that you provide the following development information when submitting feedback, including but not limited to:
  • The app type or scenario you are developing
    • Internal app
    • Third-party enterprise app
    • Third-party personal app
    • Workbench development
    • Chat open capabilities, and so on
  • A detailed description of the issue and related screenshots
  • Company name and CorpId
  • For Server API call issues, provide the following:
    • The requested API URL
    • Parameter details
    • The actual returned result
    • The expected returned result
  • For frontend API call issues, provide the following:
    • Phone model
    • Phone operating system
    • DingTalk version in use
    • The API call parameters
    • The actual returned result
    • The expected returned result