capabilities.work

Change an existing ticketing field mapping

One step with Merge. We can help you get access.

Get something done

Change an existing ticketing field mapping

with Merge

Use Merge: its Merge Subpackage Field Mapping API lets you change an existing ticketing field mapping in a single step (PATCH /ticketing/v1/field-mappings/{field_mapping_id}). capabilities.work can help you get signed up and connected.

  • Can I edit the remote URL a ticketing field mapping pulls from?
  • Is a JMESPath change allowed on a ticket field mapping I already created?
Say it to your AI assistant
  • Update ticketing mapping {field_mapping_id} to remote path {remote_url_path}.
  • Set JMES path {jmes_path} on helpdesk mapping {field_mapping_id}.
For your developer

PATCH /ticketing/v1/field-mappings/{field_mapping_id} in Merge Subpackage Field Mapping API. Full spec on APIs.io.

More you can do with Merge

List ticketing teamsGet a ticketing teamList records of a CRM custom object typeCreate a CRM custom object recordGet a CRM custom object recordGet fields required to create a custom object recordList field definitions across CRM custom objectsList companies in the HRISGet a company from the HRISList accounting itemsCreate an accounting itemGet an accounting item