Ticket Integration Destinations
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
resourcewrapper. The item’sidgoes 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 thenumfrom 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.
Fields
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.