Developer

I am attempting to create a ticket using the `comment.body` field to use Markdown formatting documented here: https://developer.zendesk.com/api-reference/ticketing/tickets/ticket_comments/#bodies Here's an example curl request with my test body: curl https://{subdomain}.zendesk.com/api/v2/tickets.json \ -d '{"ticket": {"assignee_id": 1234, "id": null, "subject": "A test email", "comment": {"body": "This message should render **markdown**"}, "requester": {"email": "redacted@rdctd.io", "id": null, "name": "redacted"}}}' \ -v -u "{username}:{password}" -X POST -H "Content-Type: application/json" The sent email is not formatted as expected. My suspicion is that the body is incorrectly translated to HTML because `html_body` is populated in the response: ...ticket audit response"events":[{"id":1234

 So i try to get looker api token using these options const loginOptions = { type: "POST", url: "https://domain.cloud.looker.com/api/4.0/login/", contentType: 'application/x-www-form-urlencoded', data: "client_id=id&client_secret=secret", }; const response = await zafClient.request(loginOptions);i got 400 bad request, when i am trying with curl/postman it's worked, currently i'm using zaf sdk version 2.0.11, anyone can help me?this is what i got in chrome dev tools: request actually go to the looker side, but it returns bad request

Hello, I'm attempting to create a timer app that will automatically add a tag to the ticket after a certain number of minutes. What works so far: Timer is able to be applied with click of a button Timer counts down correctly Timer continues even when ticket is adjusted or closed by user A Tag is applied after timer is done The issue: When the timer is done, the tag is just placed and requires a user to “Submit” the ticket After the app was updated to automatically “Submit” tickets it began throwing the error: Failed to submit ticket: {"name":"Error"} The app builder replied with: Now I can see the issue. The documentation doesn't show a ticket.submit action. Let me check if there's a different way to submit tickets or if we need to use a different approach. Looking at the documentatio

What is the recommended approach to building an app in a test sandbox them moving that app to a production environment?

We’ve noted a weird behavior of POST /api/v2/calls/{call_id}/comments endpoint. Randomly, we may get unrelated JSON back. We have hundreds of those cases daily. e.g. {'id': 26582381911698, 'type': 'Notification', 'via': {'channel': 'rule', 'source': {'from': {'deleted': False, 'title': 'Notify assignee of comment update', 'id': 29505822}, 'rel': 'trigger'}}, 'subject': '[{{ticket.account}}] Re: {{ticket.title}}', 'body': 'This ticket (#{{ticket.id}}) has been updated.\n\n{{ticket.comments_formatted}}', 'recipients': [22155944916242]} Since the introduction of the Calls API years ago, we have seen it across dozens of Zendesk instances. Can someone from the Zendesk team take a look and save our logs from those errors? 

I love this, but I'd like the app to be available in the nav bar. Is there a trick to doing that?

I'm programming a small custom App that depending on what is happening should display some popup notifications to the user. I am using the ZAF client invoke and doing the following:client.invoke('notify', 'somewarning, 'error', 30000);This by itself does work. I did however have issues finding any documentation on how to handle this through https://developer.zendesk.com/api-reference/apps/apps-core-api/client_api/#clientinvokename--args and the pages linked to from there. I only found this code snippet in an old app someone else had already done in our company. The following things I couldn't quite figure out: for the 3rd parameter, through some trial and error I found that ‘error’, ‘notification’ and ‘warning’ are options that change the color of the popups title. Are ther

Is it possible to create a ticket in Jira using the ZAFclient in a Zendesk client-side application? I'm aware that calls to the Jira API cannot be made from third-party websites for security. However, I thought ZAFclient requests going through a proxy would allow me to make authenticated requests to Jira. When making the request, I keep getting XSRF check failed error.

Hey Team, I am currently integrating the iOS Messaging Zendesk SDK by initialising the SDK with the channel key and launching the ZDKMessaging.instance.messagingViewController on successful initialisation. I am running into an issue there - The zendesk chat opens up with previous message history and flows ONLY on the first launch of the zendesk viewcontroller instance. If I close the zendesk chat, and re-open it, I see the zendesk chat view controller with a no previous messages. I can type the message in the input field at the bottom, however, once I hit send, the message isn't seen in the chat window.   Here is the attached screenshot of how the blank zendesk chat view controller is seen on the second instance.

Hi, It appears that the SupportSDK + Zendesk screens that are created from don't accurately reflect the user's choice of DarkMode. I tried the latest iOS SupportSDK + sample app(s) which at the time of this post is v5.5 here: https://github.com/zendesk/ios_sdk_demo_apps And dark mode is still not supported.  I didn't see anything in the themes either that would help solve this. Is this something that can be raised / fixed on the Zendesk side? To test / verify:  * enable Dark Mode on your iOS simulator device by opening Settings -> Developer -> Toggle ON Dark Appearance  * Run one of the iOS Support SDK apps in this Simulator  * Zendesk screens will all be white + white background Thanks!

Hey everyone!I'm currently developing a Zendesk app using Angular — that's the framework I'm most familiar and comfortable with. So far, I’ve managed to build a small form and display it within my Zendesk environment. The next step is to use the built-in ZAF methods (get, invoke, set, etc.) inside my Angular application. However, I’m running into an issue: for some reason, I can’t seem to initialize the ZAFClient — it always comes back as undefined. I’ve made my GitHub repository public in case anyone wants to take a look (note that everything is still in the early stages):🔗 https://github.com/ojuto/user-management-app1. The SDK is included in my

Hello Team, Please note that we have a mobile application, and we would like to inquire about the technical guidance required for integrating the chatbot iframe into our React Native app.  Could you please advise us on the recommended steps to proceed? We would also appreciate it if we could arrange a meeting with one of your developers to discuss these details further. Regards.

Hi,Is there a way to define a dark mode variant for the app logos?We are required to provide PNG files for logos (320x320 and 128x128), but there is no option for a dark mode variant.If we could supply SVG, we could encode support inside of the file itself, but alas this is not possible with PNG. Any ideas? Thanks!Martín.

Hi team, the hyperlink from the ticket is not being sent through the webhook.Even though I am using the HTML content field in the trigger:"ticket_data": "{{ticket.latest_public_comment_html}}",the webhook data appears as: "ticket_data": "----------------------------------------------\n\nAbinash Bhatta, Oct 7, 2025, 09:03\n\nTest\n\nAbinash Bhatta" It seems the HTML is being stripped out. I will check this further and update once I have more information.

Zendesk doesn’t offer a built-in way to remove multiple attachments at once. Handling them one by one can be slow and inefficient, especially with large volumes of files.The Attachment Redaction Add-on in the GDPR Compliance app makes this process simple and flexible. Users can set their preferences, choose what to remove, and process single tickets, users, or entire lists — all while keeping the rest of the ticket intact.Use cases it solves Freeing up storage: Quickly remove attachments that take up significant space without affecting ticket content. Data compliance: Safely redact sensitive files to meet GDPR or other privacy requirements. Inactive or outdated data cleanup: Remov

Hi Zendesk team, We noticed the Central Admin API appears in your Zendesk Public API - Postman Collection, but it’s missing from the official API reference and the endpoints are under private path: /api/admin/private/accounts/current/Despite the private path, these endpoints are reachable with an API token and are critical for us for automating SAML SSO management (e.g., rotating certificates, updating IdP settings) which we need to do programmatically. Questions: Is this API supposed to be only internal/private, or can be considered public but falling under your

This app connects to a shopify store and displays customer data and ordersProblem StatementSupporting e-commerce can require data that's stored in different tools.  Getting a customer's order status can require many data sources.  Agents can spend significant time switching apps and contexts.  Minimizing that time would increase customer satisfaction and agent productivity. Potential EnhancementsThis app is a read-only version and limited to customer and order records.  A more full-featured app could be more tightly tied with business needs, such as a refund button, a fulfillment option, a cancel feature, and additional recommended products.  This app is well-designed to iterate through additional tabs, features, controls, and further integrations. Screenshots

Onboarding a new employee requires a number of steps that require tight coordination and deadlines.  This app creates a checklist of which steps in the process have been completed and allows the agent to see what needs to be done next.Problem StatementUser onboarding requires coordination of many teams, each doing tasks that may be sequential or may be possible to execute in parallel.  Agents need to be able to see where in the process a new hire is and what steps need to be completed to successfully onboard them,Screenshots Prerequisites This prompt is looking for a user field with the ID of 41586677216283 to read the lists of “Onboarding Tasks”. &nbs

  An app which gives agent an at-a-glance view of CSAT for their entire brand for some time period, including trends.  It keeps them from having to leave Zendesk, search for tickets or guess what the trend is.  The article gives the prompt used to generate one version of this app. Problem StatementWhen working on a ticket for a customer, an agent may want to know the sentiment over time of the customer, as well as comments made on the customer's tickets after the ticket closed.  Doing so may take them away from the customer's current reply and might involve hunting through older tickets and checking for comments.   If this retreival can be automated to keep the agent focused on the customer , it will improve response time and provide agents with real-time help in understanding this customer in-depth. Screenshots

Hello! We are currently integrating your messaging SDK into our Unity application and have encountered a technical issue with the GetUnreadMessageCountAsync methodHere are the details of the issue:In our usage GetUnreadMessageCountAsync(Action onUnreadCountChanged, bool shouldSubscribe) returns 0 until the user opens the support conversation.We attempted subscribing to the WebSocket event outside of the conversation, but this did not resolve the issue.The method only starts returning valid information after the user has opened the support conversation. Our goal is to notify users of new responses from support agents by displaying a notification dot above the support button. However, the current behaviour of the SDK prevents us from achieving this functionality. Expected Behaviour:We expect that the GetUnreadMessageCountAsync method should return the actual u

We are seeing a crash in the Zendesk Messaging Android SDK when the conversation screen renders HTML content. The app throws java.lang.AbstractMethodError referencing android.text.Html$TagHandler.handleTag(boolean, java.lang.String, android.text.Editable, org.xml.sax.XMLReader) during HTML to Spanned conversion.  Zendesk Messaging (Android) SDK version：zendesk.messaging:messaging-android:2.34.0 Crash Detail：          Fatal Exception: java.lang.AbstractMethodError: abstract method "void android.text.Html$TagHandler.handleTag(boolean, java.lang.String, android.text.Editable, org.xml.sax.XMLReader)"      at android.text.HtmlToSpannedConverter.handleStartTag(Html.java:842)      at android.text.HtmlToSpannedConverter.startElement(Html.java:1243)      at org.ccil.cowan.tagsoup.Pars

Recipes for App Builder work best if readers can discover them and can tell quickly if this recipe solves their problem.  Start with a summary so that readers can tell quickly what the recipe is about.  If you were publishing this recipe to the Zendesk App Marketplace, this is the quick blurb to get readers to read on.  A recipe does not need all these sections to be helpful to other app builders.  You can write a Problem Statement and a Prompt and have enough to help people make a similar app.Make sure to give your recipe a clear title, since that's going to be prominently displayed and found in searches.  start with “Recipe: ”, then something helpful like the title of the app or the purpose, then “app” or “application”.  Making your recipe easy to find helps everyone.

Zendesk does not allow iframing of a web application.Zendesk prevents the iframing of Zendesk by setting an HTTP header (X-Frame-options) to SAMEORIGIN for all server responses.  

An app which limits the reassignment process so that a ticket that is assigned to an agent cannot be reassigned to a group, only another agent.  The article gives the prompt and the generated blueprint.Problem StatementSome businesses do not wish to allow a Zendesk ticket to be reassigned to a group after it has already been assigned to an agent.  They wish to be able to reassign tickets, but only to actual agents.  This app is designed to restrict agents from assigning a ticket to a group.  Potential EnhancementsThe admin creating this app could add more restrictions or conditions on the restrictions, such as restrictions only for a particular agent group or allowing group reassignment for some agent groups but not others, a status requirement (e.g. 'only allow group reassignment if ticket status is New'), or any other customer-specific workflow. ScreenshotsThese are typi

Using JWT Authentication, it would be expected that once a request is marked “read” that it will remain “read”. However, if a user acquired a new JWT, it seems the “read” state of all requests is lost. The user experiences a total reset of the “read” status of all tickets, causing confusion and annoyance.  Create a ticket via SDK Channel with JWT authentication Have an agent respond to the ticket Get updates for device View all requests Refresh JWT (in our case, logout then login of app) Get updates for device Notice all previously “read” requests are “unread” Is there a way to avoid this issue?