> For the complete documentation index, see [llms.txt](https://docs.dinmo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dinmo.io/integrations/destination-platforms/zendesk.md).

# Zendesk

Sending data to Zendesk: Step-by-Step Guide

## Supported Destination Services

DinMo supports the following destination services:

* [Synchronize users](https://docs.dinmo.io/integrations/destination-platforms/zendesk/synchronize-users.md)
* [Synchronize custom objects](https://docs.dinmo.io/integrations/destination-platforms/zendesk/synchronize-custom-objects-data.md)

Please refer to the dedicated documentation page for more information.

## Authentication to Zendesk

DinMo supports two authentication methods:

* **OAuth (client credentials)**, recommended for new and existing destinations.
* **API token (legacy)**, available temporarily for connections that already have a valid Zendesk API token.

Both methods support the Synchronize users and Synchronize custom objects destination services.

### Connect with OAuth

New Zendesk destinations use OAuth by default.

1. In Zendesk Admin Center, go to **Apps and integrations > APIs > OAuth clients**.
2. Create a **confidential** OAuth client.
3. Allow the client to use the `read` and `write` scopes.
4. Copy the client **Identifier** and **Secret**. Zendesk displays the secret only once.
5. In DinMo, create or edit the Zendesk destination and select **OAuth (client credentials)**.
6. Enter the **Zendesk Subdomain**, **OAuth client Identifier**, and **OAuth client Secret**.
7. Test the connection, then save the destination.

DinMo obtains and renews OAuth access tokens automatically, including after long periods without synchronization.

Actions performed through the connection are attributed in Zendesk to the user who created the OAuth client. Use a dedicated service account when this attribution matters.

### Migrate an existing destination to OAuth

Edit the existing Zendesk destination and change its authentication method to **OAuth (client credentials)**. Enter the client Identifier and Secret, test the connection, and save your changes.

Keep the existing destination rather than creating a new one. Changing its authentication method preserves its activations, mappings, and synchronization configuration.

### Find your Zendesk subdomain

The subdomain appears in your Zendesk URL. For example, if your URL is `https://mycompany.zendesk.com/agent/dashboard`, enter `mycompany`.

### Use a legacy API token

If the destination already uses a valid Zendesk API token, select **API token (legacy)** and provide the Zendesk account email address, existing API token, and subdomain.

Zendesk no longer allows new API tokens to be created. Existing tokens can also be deactivated after a period of inactivity, and all remaining API tokens will be permanently deactivated on April 30, 2027. Migrate existing destinations to OAuth before that date.

For details, see [Migrating from API tokens to OAuth access tokens](https://developer.zendesk.com/documentation/authentication/oauth-migration/).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dinmo.io/integrations/destination-platforms/zendesk.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
