large_Wavin case study background.png

medium_Wavin case study background.png

small_Wavin case study background.png

thumbnail_Wavin case study background.png

Wavin case study background.png

Learn how Wavin connected with their end-customers via a branded loyalty app and grew their user base 17x in the first 6 months.

large_Wavin rewards app 1.png

medium_Wavin rewards app 1.png

small_Wavin rewards app 1.png

thumbnail_Wavin rewards app 1.png

Wavin rewards app 1.png

Connect your loyalty program in Zendesk without researching its API, registering in a developer program, and getting your application approved. We take care of authentication, secure credentials storage, and token refreshes so you don't have to.

Zendesk

<p>Shows the settings that are available for the account.</p>
<h4>Allowed For</h4>
<ul>
<li>Agents</li>
</ul>


Show Settings

<p>Updates settings for the account. See <a>JSON Format</a> above for the settings you can update.</p>
<h4>Allowed For</h4>
<ul>
<li>Admins</li>
</ul>


Update Account Settings

Create Trial Account

<p>Zendesk Support credentials are not required to access this endpoint. You can use any Zendesk Support subdomain.</p>
<p>Returns "true" if the subdomain is available.</p>


Verify Subdomain Availability

<p>Lists ticket activities in the last 30 days affecting the agent making the request.
Also sideloads the following arrays of user records:</p>
<ul>
<li>actors - All actors involved in the listed activities</li>
<li>users - All users involved in the listed activities</li>
</ul>
<h4>Pagination</h4>
<ul>
<li>Cursor pagination (recommended)</li>
<li>Offset pagination</li>
</ul>
<p>See <a>Pagination</a>.</p>
<p>Returns a maximum of 100 records per page.</p>
<h4>Allowed For</h4>
<ul>
<li>Agents</li>
</ul>


List Activities

<p>Lists a specific activity.</p>
<h4>Allowed For</h4>
<ul>
<li>Agents</li>
</ul>


Show Activity

Returns an approximate count of ticket activities in the last 30 days affecting the agent making the request. If the count exceeds 100,000, the count will return a cached result. This cached result will update every 24 hours.

The `count[refreshed_at]` property is a timestamp that indicates when the count was last updated.

**Note**: When the count exceeds 100,000, `count[refreshed_at]` may occasionally be null.
This indicates that the count is being updated in the background, and `count[value]` is limited to 100,000 until the update is complete.

#### Allowed For
* Agents

Count Activities

Shows attachment details. You can get the value of the `attachment_id` parameter by listing the ticket's comments.
See [List Comments](/api-reference/ticketing/tickets/ticket_comments/#list-comments). Each comment
in the list has an `attachments` list that specifies an `id` for each attachment.


 #### Allowed for

 * Agents


Show Attachment

Toggles enabling or restricting agent access to attachments with detected malware.

#### Allowed For

* Admins


Update Attachment for Malware

#### Allowed For

* Admins on accounts that have audit log access

#### Pagination

* Cursor pagination (recommended)
* Offset pagination

See [Pagination](/api-reference/introduction/pagination/).

Returns a maximum of 100 records per page.


List Audit Logs

#### Allowed For

* Admins on accounts that have audit-log access


Show Audit Log

#### Allowed For

* Admins on accounts that have audit log access


Export Audit Logs

Lists all automations for the current account.

#### Allowed For

* Agents

#### Available Parameters

You can pass in any combination of the following optional filters:

| Name       | Type    | Comment
| ---------- | ------- | -------
| active     | boolean | Only active automations if true, inactive automations if false
| sort_by    | string  | Possible values are "alphabetical", "created_at", "updated_at", "usage_1h", "usage_24h", or "usage_7d". Defaults to "position"
| sort_order | string  | One of "asc" or "desc". Defaults to "asc" for alphabetical and position sort, "desc" for all others

#### Sideloads

The following sideloads are supported. The usage sideloads are only supported on the Support Professional or Suite Growth plan or above.

| Name             | Will sideload
| ---------------- | -------------
| app_installation | The app installation that requires each automation, if present
| permissions      | The permissions for each automation
| usage_1h         | The number of times each automation has been used in the past hour
| usage_24h        | The number of times each automation has been used in the past day
| usage_7d         | The number of times each automation has been used in the past week
| usage_30d        | The number of times each automation has been used in the past thirty days

#### Pagination

- Cursor pagination (recommended)
- Offset pagination

See [Pagination](/api-reference/introduction/pagination/).

Returns a maximum of 100 records per page.


List Automations

Creates an automation.

New automations must be unique and have at least one condition that is true only once or an action that nullifies at least one of the conditions. Active automations can have overlapping conditions but can't be identical.

The request must include the following conditions in the `all` array:

- At least one time-based condition
- At least one condition that checks one of the following fields: `status`, `type`, `group_id`, `assignee_id`, or `requester_id`.

#### Allowed For

* Agents


Create Automation

Lists all active automations.

#### Allowed For

* Agents

#### Available Parameters

You can pass in any combination of the following optional filters:

| Name       | Type   | Comment
| ---------- | ------ | -------
| sort_by    | string | Possible values are "alphabetical", "created_at", "updated_at", "usage_1h", "usage_24h", or "usage_7d". Defaults to "position"
| sort_order | string | One of "asc" or "desc". Defaults to "asc" for alphabetical and position sort, "desc" for all others

#### Sideloads

The following sideloads are supported:

| Name             | Will sideload
| ---------------- | -------------
| app_installation | The app installation that requires each automation, if present
| permissions      | The permissions for each automation
| usage_1h         | The number of times each automation has been used in the past hour
| usage_24h        | The number of times each automation has been used in the past day
| usage_7d         | The number of times each automation has been used in the past week
| usage_30d        | The number of times each automation has been used in the past thirty days


List Active Automations

Deletes the automations corresponding to the provided comma-separated list of IDs.

**Note**: You might be restricted from deleting some default automations. If included in a bulk deletion, the unrestricted automations will be deleted.

#### Allowed For

* Agents

#### Request Parameters

The DELETE request takes one parameter, an `ids` object that lists the automations to delete.

| Name | Description
| ---- | -----------
| ids  | The IDs of the automations to delete

#### Example request

```js
{
  "ids": "25,23,27,22"
}
```


Bulk Delete Automations

#### Pagination

* Offset pagination only

See [Using Offset Pagination](/api-reference/ticketing/introduction/#using-offset-pagination).

#### Allowed For

* Agents

#### Sideloads

The following sideloads are supported. For more information, see [Side-loading](/documentation/ticketing/using-the-zendesk-api/side_loading/).

| Name             | Will sideload
| ---------------- | -------------
| app_installation | The app installation that requires each automation, if present
| permissions      | The permissions for each automation
| usage_1h         | The number of times each automation has been used in the past hour
| usage_24h        | The number of times each automation has been used in the past day
| usage_7d         | The number of times each automation has been used in the past week
| usage_30d        | The number of times each automation has been used in the past thirty days


Search Automations

**Note**: You might be restricted from updating some default automations. If included in a bulk update, the unrestricted automations will be updated.

#### Allowed For

* Agents

#### Request Parameters

The PUT request expects an `automations` object that lists the automations to update.

Each automation may have the following properties:

| Name     | Mandatory | Description
| -------- | --------- | -----------
| id       | yes       | The ID of the automation to update
| position | no        | The new position of the automation
| active   | no        | The active status of the automation (true or false)

#### Example Request

```js
{
  "automations": [
    {"id": 25, "position": 3},
    {"id": 23, "position": 5},
    {"id": 27, "position": 9},
    {"id": 22, "position": 7}
  ]
}
```


Update Many Automations

Show Automation

Updates an automation.

Updated automations must be unique and have at least one condition that is true only once or an action that nullifies at least one of the conditions. Active automations can have overlapping conditions but can't be identical.

The request must include the following conditions in the `all` array:
- At least one time-based condition
- At least one condition that checks one of the following fields: 'status', 'type', 'group_id', 'assignee_id', or 'requester_id'

**Note**: Updating a condition or action updates both the `conditions` and `actions` arrays, clearing all existing values of both arrays. Include all your conditions and actions when updating any condition or action.
**Note**: You might be restricted from updating some default automations.

#### Allowed For

* Agents


Update Automation

**Note**: You might be restricted from deleting some default automations.

#### Allowed For

* Agents


Delete Automation

List Bookmarks

Create Bookmark

#### Allowed For
- Agents (own bookmarks only)

If the bookmark already exists with a specified ticket id, the response status will be `http Status: 200 OK`.

Delete Bookmark

Returns a list of all brands for your account sorted by name.

#### Allowed for

* Admins, Agents

List Brands

Create Brand

Returns a JSON object determining whether a host mapping is valid for a given subdomain.

#### Allowed for

* Admins

Check Host Mapping Validity

Returns a brand for your account.

#### Allowed for

* Admins, Agents

Show a Brand

Returns an updated brand.

#### Allowed for
* Admins

#### Updating a Brand's Image
A brand image can be updated by uploading a local file using the update brand endpoint. See the **Using curl** sections below for more information.

Update a Brand

Deletes a brand.

#### Allowed for
- Admins

Delete a Brand

Returns a JSON object determining whether a host mapping is valid for the given brand.

#### Allowed for
- Admins

Check Host Mapping Validity for an Existing Brand

#### Allowed For
* Agents

### Creating tickets

#### Introduction

Creating tickets using Talk Partner Edition follows the same conventions as the Create Ticket endpoint. See [Create Ticket](/api-reference/ticketing/tickets/tickets/#create-ticket).

#### Request parameters

The POST request takes a mandatory `ticket` object that lists the values to set when the ticket is created.
You may also include an optional `display_to_agent` value such as the ID of the agent that will see the newly created ticket.

Tickets created using this endpoint must have a `via_id` parameter. See the following
section for possible values.

#### Zendesk Talk Integration Via IDs

Tickets created using this endpoint must have one of the following `via_id` parameters:

| ID       | Description
| ---------| -------------
| 44       | Voicemail
| 45       | Phone call (inbound)
| 46       | Phone call (outbound)

### Creating voicemail tickets
#### Request parameters

The POST request takes a mandatory `ticket` object that lists the values to set when the ticket is created.
The ticket must have a `voice_comment` with the following values:

| Name               | Type                  | Comment
| ------------------ | ----------------------| -------
| from               | string                | Incoming phone number
| to                 | string                | Dialed phone number
| recording_url      | string                | URL of the recording
| started_at         | date                  | [ISO 8601](http://en.wikipedia.org/wiki/ISO_8601) timestamp of the call starting time
| call_duration      | integer               | Duration in seconds of the call
| answered_by_id     | integer               | The agent who answered the call
| transcription_text | string                | Transcription of the call (optional)
| location           | string                | Location of the caller (optional)

Create Ticket or Voicemail Ticket

Allows you to instruct an agent's browser to open a ticket.

When the message is successfully delivered to an agent's browser:

```http
Status: 200 OK
```

When `agent_id` or `ticket_id` is invalid:

```http
Status: 404 Not Found
```

#### Allowed For
* Agents

Open Ticket in Agent's Browser

Allows you to instruct an agent's browser to open a user's profile.

When the message is successfully delivered to an agent's browser:

```http
Status: 200 OK
```

When `agent_id` or `ticket_id` is invalid:

```http
Status: 404 Not Found
```

#### Allowed For
* Agents

Open a User's Profile in an Agent's Browser

#### Availability

* Accounts on the Enterprise plan or above

#### Allowed For

* Agents


List Custom Roles

#### Availability

* Accounts on the Enterprise plan or above

#### Allowed For

* Administrators


Create Custom Role

Show Custom Role

#### Availability

* Accounts on the Enterprise plan or above

#### Allowed Forx

* Administrators


Update Custom Role

Delete Custom Role

Lists all undeleted custom ticket statuses for the account. No pagination is provided.

You can't have more than 300 custom ticket statuses at a time.

#### Allowed For

* End Users


List Custom Ticket Statuses

Takes a `custom_status` object that specifies the custom ticket status properties to create.

#### Allowed For

* Admins


Create Custom Ticket Status

Returns the custom ticket status object.

#### Allowed For

* End Users


Show Custom Ticket Status

Takes a `custom_status` object that specifies the properties to update.

#### Allowed For

* Admins


Update Custom Ticket Status

Returns a maximum of 100 deleted tickets per page. See [Pagination](/api-reference/introduction/pagination/).

The results includes all deleted (and not yet archived) tickets that
have not yet been [scrubbed](https://support.zendesk.com/hc/en-us/articles/4408845703194#topic_fv5_w51_sdb) in the past 30 days. Archived tickets are
not included in the results. See [About archived tickets](https://support.zendesk.com/hc/en-us/articles/203657756)
in the Support Help Center.

The tickets are ordered chronologically by created date, from oldest to newest.
The first ticket listed may not be the oldest ticket in your
account due to [ticket archiving](https://support.zendesk.com/hc/en-us/articles/203657756).

#### Pagination

- Cursor pagination (recommended)
- Offset pagination

See [Pagination](/api-reference/introduction/pagination/).

Returns a maximum of 100 records per page.

#### Allowed For

* Agents

#### Rate Limit

You can make 10 requests every 1 minute using this endpoint.
When making requests beyond page 100, you can make 5 requests every 1 minute.
The rate limiting mechanism behaves as described in
[Monitoring your request activity](/api-reference/ticketing/account-configuration/usage_limits/#monitoring-your-request-activity) in the API introduction.

List deleted tickets

Permanently deletes up to 100 soft-deleted tickets. See [Soft delete](https://support.zendesk.com/hc/en-us/articles/4408834005530#topic_zrm_wbj_1db)
in the Zendesk GDPR docs. To soft delete tickets, use the [Bulk Delete Tickets](#bulk-delete-tickets) endpoint.

This endpoint accepts a comma-separated list of up to 100 ticket ids. It enqueues
a ticket deletion job and returns a payload with the jobs status.

If one ticket fails to be deleted, the endpoint still attempts to delete the others. If the job succeeds,
the tickets that were successfully deleted are permanently deleted. This operation can't be undone.

This endpoint returns a `job_status` [JSON object](/api-reference/ticketing/ticket-management/job_statuses/#json-format) and queues a background job to do the work.
Use the [Show Job Status](/api-reference/ticketing/ticket-management/job_statuses/#show-job-status) endpoint to check for the job's completion.

#### Allowed For

* Agents

Delete multiple tickets permanently

Restore previously deleted tickets in bulk

Permanently deletes a soft-deleted ticket. See [Soft delete](https://support.zendesk.com/hc/en-us/articles/4408834005530#topic_zrm_wbj_1db)
in the Zendesk GDPR docs. To soft delete a ticket, use the [Delete Ticket](#delete-ticket) endpoint.

This endpoint enqueues a ticket deletion job and returns a payload with the jobs status.

If the job succeeds, the ticket is permanently deleted. This operation can't be undone.

This endpoint returns a `job_status` [JSON object](/api-reference/ticketing/ticket-management/job_statuses/#json-format) and queues a background job to do the work.
Use the [Show Job Status](/api-reference/ticketing/ticket-management/job_statuses/#show-job-status) endpoint to check for the job's completion.

#### Allowed For

* Agents

Delete ticket permanently

Restore a previously deleted ticket

Returns deleted users, including permanently deleted users.

If the results contains permanently deleted users, the users' properties
that normally contain personal data, such as `email` and `phone`,
are null. The `name` property is "Permanently Deleted User".

#### Pagination

* Cursor pagination (recommended)
* Offset pagination

See [Pagination](/api-reference/introduction/pagination/).

Returns a maximum of 100 records per page.

#### Allowed For

* Agents


List Deleted Users

Returns an approximate count of deleted users, including permanently deleted users. If the count exceeds 100,000, it is updated every 24 hours.

The response includes a `refreshed_at` property in a `count` object that contains a timestamp indicating when the count was last updated.

**Note**: When the count exceeds 100,000, `count[refreshed_at]` may occasionally be null.
This indicates that the count is being updated in the background, and `count[value]` is limited to 100,000 until the update is complete.

#### Allowed For

* Agents


Count Deleted Users

Returns users that have been deleted but not permanently yet. See [Permanently Delete User](#permanently-delete-user).

#### Allowed For:

* Agents


Show Deleted User

Before permanently deleting a user, you must delete the user first. See [Delete User](/api-reference/ticketing/users/users/#delete-user).

WARNING: Permanently deleting a user deletes all of their information. This information is not recoverable.

#### Permanent user deletion rate limit

You can permanently delete 700 users every 10 minutes.
The rate limiting mechanism behaves as described in
[Rates Limits](/api-reference/introduction/rate-limits/#monitoring-your-request-activity) in the API introduction.
Zendesk recommends that you obey the Retry-After header values.

#### Allowed For

* Agents, with restrictions on certain actions


Permanently Delete User

Returns all the variants of the specified dynamic content item.

#### Allowed For

* Admins
* Agents who have permission to manage dynamic content


List Variants

You can only create one variant for each locale id. If a locale variant already exists, the request is rejected.

#### Allowed For

* Admins, Agents


Create Variant

Create Many Variants

Updates one or more variants. See [Update Variant](/api-reference/ticketing/ticket-management/dynamic_content_item_variants/#update-variant).

You must specify the variants by id in the body. To get the variant ids, see [List Variants](/api-reference/ticketing/ticket-management/dynamic_content_item_variants/#list-variants).

#### Allowed For

* Admins, Agents


Update Many Variants

Show Variant

Updates the specified variant. You don't need to include all the properties. If you just want to update content, for example, then include just that.

You can't switch the active state of the default variant of an item. Similarly, you can't switch the default to false if the variant is the default. You must make another variant default instead.

#### Allowed For

* Admins, Agents


Update Variant

Delete Variant

Returns a list of all dynamic content items for your account if accessed as an admin or agents who have permission to manage dynamic content.

#### Allowed For

* Admins, Agents


List Items

Create a new content item, with one or more variants in the item's `variants` array. See [Specifying item variants](#specifying-item-variants).

The `default_locale_id` and variant `locale_id` values must be one of the locales the account has active. You can get the list with the [List Locales](/api-reference/ticketing/account-configuration/locales/#list-locales) endpoint.

#### Allowed For

* Admins, Agents


Create Item

#### Stability

* Development

#### Allowed For

* Admins, Agents


Show Many Items

Show Item

The only attribute you can change is the name.

To add a variant to the item, or to update or delete the variants of the item, use the [Item Variants API](/api-reference/ticketing/ticket-management/dynamic_content_item_variants/#update-many-variants).

#### Allowed For

* Admins, Agents


Update Item

Delete Item

#### Pagination

* Cursor pagination (recommended)
* Offset pagination

See [Pagination](/api-reference/introduction/pagination/).

Returns a maximum of 100 records per page.

#### Allowed For:

* Agents


List Memberships

Assigns an agent to a given group.

#### Allowed For

* Admins


Create Membership

Returns a maximum of 100 group memberships per page.

#### Pagination

* Cursor pagination (recommended)
* Offset pagination

See [Pagination](/api-reference/introduction/pagination/).

Returns a maximum of 100 records per page.

#### Allowed For:

* Agents


List Assignable Memberships

Assigns up to 100 agents to given groups.

#### Allowed For

* Admins

#### Response

This endpoint returns a `job_status` [JSON object](/api-reference/ticketing/ticket-management/job_statuses/#json-format) and queues a background job to do the work. Use the [Show Job Status](/api-reference/ticketing/ticket-management/job_statuses/#show-job-status) endpoint to check for the job's completion.


Bulk Create Memberships

Immediately removes users from groups and schedules a job to unassign all working tickets that are assigned to the given user and group combinations.

#### Allowed For

* Admins


Bulk Delete Memberships

The 'id' is the group membership id, not a group id.

#### Allowed For

* Agents


Show Membership

Immediately removes a user from a group and schedules a job to unassign all working tickets that are assigned to the given user and group combination.

#### Allowed For

* Admins


Delete Membership

#### Pagination

* Cursor pagination (recommended)
* Offset pagination

See [Pagination](/api-reference/introduction/pagination/).

Returns a maximum of 100 records per page.

#### Allowed For

* Admins
* Agents


List Groups

Create Group

List Assignable Groups

Returns an approximate count of groups. If the count exceeds 100,000, it is updated every 24 hours.

The `refreshed_at` property of the `count` object is a timestamp that indicates when the count was last updated.

**Note**: When the count exceeds 100,000, `refreshed_at` may occasionally be null. This indicates that the count is being updated in the background, and the `value` property of the `count` object is limited to 100,000 until the update is complete.

#### Allowed For

* Admins
* Agents


Count Groups

Show Group

Update Group

Delete Group

Ticket Import

Accepts an array of up to 100 ticket objects.

#### Allowed For

* Admins

Ticket Bulk Import

Returns a stream of changes that occurred on routing attribute values.

#### Allowed For

* Admins

#### Parameters

Optional

| Name   | Type   | Comment
| ------ | ------ | -------
| cursor | string | The `cursor` parameter is a non-human-readable argument you can use to move forward or backward in time. The cursor is a read-only URL parameter that's only available in API responses. See [Pagination](#pagination).


Incremental Attributes Values Export

Returns a stream of changes that occurred on routing attributes.

#### Allowed For

* Admins

#### Parameters

Optional


| Name   | Type   | Comment
| ------ | ------ | -------
| cursor | string | The `cursor` parameter is a non-human-readable argument you can use to move forward or backward in time. The cursor is a read-only URL parameter that's only available in API responses. See [Pagination](#pagination).


Incremental Attributes Export

Returns a stream of changes that occurred on routing instance values. Changes are grouped by `attribute_value_id`,
with unassociate type events listed with associate type events by the associate event’s timestamp.

#### Allowed For

* Admins

#### Parameters

Optional

| Name   | Type   | Comment
| ------ | ------ | -------
| cursor | string | The `cursor` parameter is a non-human-readable argument you can use to move forward or backward in time. The cursor is a read-only URL parameter that's only available in API responses. See [Pagination](#pagination).


Incremental Instance Values Export

Returns the tickets that changed since the start time. For more information,
see [Exporting tickets](/documentation/ticketing/managing-tickets/using-the-incremental-export-api#exporting-tickets) in [Using the Incremental Exports API](/documentation/ticketing/managing-tickets/using-the-incremental-export-api).

This endpoint supports time-based incremental exports.
For more information, see [Time-based incremental exports](/documentation/ticketing/managing-tickets/using-the-incremental-export-api#time-based-incremental-exports) in [Using the Incremental Exports API](/documentation/ticketing/managing-tickets/using-the-incremental-export-api). You can also return tickets using cursor-based pagination. See [Incremental Ticket Export, Cursor Based](#incremental-ticket-export-cursor-based).

The results include tickets that were updated by the system. See
[Excluding system-updated tickets](/documentation/ticketing/managing-tickets/using-the-incremental-export-api#excluding-system-updated-tickets-time-based-exports) in [Using the Incremental Exports API](/documentation/ticketing/managing-tickets/using-the-incremental-export-api).

The endpoint can return tickets with an `updated_at` time that's earlier than the
`start_time` time. The reason is that the API compares the `start_time` with the ticket's
`generated_timestamp` value, not its `updated_at` value. The `updated_at` value is
updated only if the update generates a [ticket event](#incremental-ticket-event-export).
The `generated_timestamp` value is updated for all ticket updates, including system
updates. If a system update occurs after a ticket event, the unchanged
`updated_at` time will become earlier relative to the updated `generated_timestamp`
time.

#### Allowed For

 * Admins

#### Sideloading

See [Tickets sideloads](/documentation/ticketing/using-the-zendesk-api/side_loading/#supported-endpoints). For performance reasons,
`last_audits` sideloads aren't supported.


Incremental Ticket Export, Time Based

Returns the tickets that changed since the start time. For more information,
see [Exporting tickets](/documentation/ticketing/managing-tickets/using-the-incremental-export-api#exporting-tickets) in [Using the Incremental Exports API](/documentation/ticketing/managing-tickets/using-the-incremental-export-api).

This endpoint supports cursor-based incremental exports.
Cursor-based exports are highly encouraged because they provide more consistent performance and
response body sizes. For more information, see [Cursor-based incremental exports](/documentation/ticketing/managing-tickets/using-the-incremental-export-api#cursor-based-incremental-exports) in [Using the Incremental Exports API](/documentation/ticketing/managing-tickets/using-the-incremental-export-api).



#### Allowed For

 * Admins

#### Sideloading

See [Tickets sideloads](/documentation/ticketing/using-the-zendesk-api/side_loading/#supported-endpoints). For performance reasons,
`last_audits` sideloads aren't supported.


Incremental Ticket Export, Cursor Based

#### Allowed For

 * Admins

#### Sideloading

See [Users sideloads](/documentation/ticketing/using-the-zendesk-api/side_loading/#supported-endpoints).


Incremental User Export, Time Based

Incremental User Export, Cursor Based

Use this endpoint to test the incremental export format. It's more strict in terms of rate limiting,
at 10 requests per 20 minutes instead of 10 requests per minute. It also returns only up to 50
results per request. Otherwise, it's identical to the above APIs.

Use the `incremental_resource` parameter to specify the resource. Possible values are "tickets", "ticket_events", "users", or "organizations".


Incremental Sample Export

#### Allowed For

 * Admins

#### Sideloading

See [Organizations sideloads](/documentation/ticketing/using-the-zendesk-api/side_loading/#supported-endpoints).


Incremental Organization Export

Returns a stream of changes that occurred on tickets. Each event is tied
to an update on a ticket and contains all the fields that were updated in that
change. For more information, see:

- [Exporting ticket events](/documentation/ticketing/managing-tickets/using-the-incremental-export-api#exporting-ticket-events) in [Using the Incremental Exports API](/documentation/ticketing/managing-tickets/using-the-incremental-export-api)
- [Time-based incremental exports](/documentation/ticketing/managing-tickets/using-the-incremental-export-api#time-based-incremental-exports) in [Using the Incremental Exports API](/documentation/ticketing/managing-tickets/using-the-incremental-export-api)

You can include comments in the event stream by using the `comment_events`
sideload. See Sideloading below. If you don't specify the sideload, any comment
present in the ticket update is described only by Boolean `comment_present`
and `comment_public` object properties in the event's `child_events` array.
The comment itself is not included.

#### Allowed For

 * Admins

#### Sideloading

The endpoint supports the `comment_events` sideload. Any comment present in the ticket
update is listed as an object in the event's `child_events` array. Example:

```js
"child_events": [
  {
    "id": 91048994488,
    "via": {
      "channel": "api",
      "source": {"from":{},"to":{},"rel":null}},
    "via_reference_id":null,
    "type": "Comment",
    "author_id": 5031726587,
    "body": "This is a comment",
    "html_body": "&lt;div class="zd-comment"&gt;&lt;p dir="auto"&gt;This is a comment&lt;/p&gt;",
    "public": true,
    "attachments": [],
    "audit_id": 91048994468,
    "created_at": "2009-06-25T10:15:18Z",
    "event_type": "Comment"
  },
  ...
],
...
```


Incremental Ticket Event Export

Returns ticket metric events that occurred on or after the start time.

Cursor pagination returns a maximum of 100 records per page. Events are listed in chronological order.

If the results are not paginated, events will be returned as a time-based incremental export.

See [Time-based incremental exports](/documentation/ticketing/managing-tickets/using-the-incremental-export-api#time-based-incremental-exports).

#### Pagination
* Cursor pagination
* No pagination

See [Pagination](/api-reference/introduction/pagination/).

#### Allowed For

* Admins

List Ticket Metric Events

Shows the current statuses for completed background jobs.

#### Allowed For:

* Agents


List Job Statuses

Shows the status of a background job.

A job may no longer exist to query. Zendesk only logs the last 100 jobs. Jobs also expire within an hour.

#### Allowed For:

* Agents


Show Job Status

Accepts a comma-separated list of job status ids.

#### Allowed For:

* Agents


Show Many Job Statuses

Lists the translation locales available for the account.

**Note**: You can alter the list by passing an updated `locale_ids` array to the [Update Account Settings](/api-reference/ticketing/account-configuration/account_settings/#update-account-settings) endpoint.

#### Allowed For

* Anyone


List Locales

Show Locale

Lists the translation locales that have been localized for agents on a specific account.

#### Allowed For

* Anyone


List Locales for Agent

This works like [Show Locale](#show-locale), but instead of taking a locale id as an argument, it renders the locale of the user performing the request.

#### Allowed For

* Anyone


White Label Loyalty + Zendesk integration

About Zendesk

Similar Integrations

Basecamp

Intercom

Clickup

SuperOffice

Benefits of White Label Loyalty + Zendesk

Integrate now!

Automate desired actions with Zendesk

Show Settings

Allowed For

List Activities

Pagination

Allowed For

Update Account Settings

Allowed For

Show Activity

Allowed For

Create Trial Account

Verify Subdomain Availability

Call and retrieve data from Zendesk

Wavin

Choose White Label Loyalty and become a loyalty leader

	list	find By Id	create	update	delete
Articles
Categories
Organizations
Permission Groups
Sections