> This page is for API Reference & Tools.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.moveworks.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.moveworks.com/_mcp/server.

# Ticket Integration Destinations

> Create, read and update Ticket Integration Destinations through the Moveworks Configuration API: endpoints, fields and examples.

`tool.ticket.integration.destinations`

Where tickets are filed (one per table/queue). Referenced by mappers and workflows by id.

* **Endpoint:** `/tool/ticket/integration/destinations`  |  **Methods:** GET, PATCH, POST
* **Request shape:** fields go at the top level of the JSON body, with no `resource` wrapper. The item's `id` goes in the URL for reads and updates, not in the body.
* **Updates:** a JSON merge-patch. Send only the fields you change, plus `version: {num, change_description}` with the `num` from your last read. Lists and maps you send replace the stored ones whole.

### Endpoints

All paths are relative to `https://api.moveworks.ai/configurations/v1alpha1`. Each endpoint page lists the request and response schema, an example, and the errors it can return.

| Method  | Path                                         | Endpoint reference                                                                                                                                        |
| ------- | -------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `GET`   | `/tool/ticket/integration/destinations`      | [List ticket integration destinations](/api-reference/configuration-api/ticketing/ticket-integration-destinations/list-ticket-integration-destinations)   |
| `POST`  | `/tool/ticket/integration/destinations`      | [Create ticket integration destination](/api-reference/configuration-api/ticketing/ticket-integration-destinations/create-ticket-integration-destination) |
| `GET`   | `/tool/ticket/integration/destinations/{id}` | [Get ticket integration destination](/api-reference/configuration-api/ticketing/ticket-integration-destinations/get-ticket-integration-destination)       |
| `PATCH` | `/tool/ticket/integration/destinations/{id}` | [Update ticket integration destination](/api-reference/configuration-api/ticketing/ticket-integration-destinations/update-ticket-integration-destination) |

### Fields

| Field          | Type    | Required  | Notes                                                                                                                                                                           |
| -------------- | ------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `id`           | string  | read-only | Unique ID of this configuration, assigned by the server.                                                                                                                        |
| `connector_id` | string  | ✅         | Connector for the ticketing system that tickets are filed in. Cannot be changed after creation. ID of an existing connector (GET /configurations/v1alpha1/platform/connectors). |
| `updated_time` | string  | read-only | When the configuration was last updated.                                                                                                                                        |
| `updated_by`   | string  | read-only | Who last updated the configuration.                                                                                                                                             |
| `version`      | Version | ✅         | Document version. On update, send back the num from your last read.                                                                                                             |

Set at most one of `bmc_remedy_config`, `cherwell_config`, `fresh_service_config`, `jira_service_desk_config`, `service_now_config`, `zendesk_config`, `wolken_config`, `manage_engine_config`, `ivanti_config`, `salesforce_config`, `sysaid_config`, `solarwinds_config`, `fresh_desk_config`, `connect_wise_config`, `workday_config`, `bmc_remedyforce_config`, `workday_itsm_config`, `symphony_config`, `microsoft_dynamics_config`, `ticket_gateway_config`.

### Example create body

```json
{
  "connector_id": "<connector-uuid>",
  "service_now_config": {
    "table_name": "incident"
  },
  "version": {
    "change_description": "Create ticket integration destination"
  }
}
```