All Collections
Using PATCH endpoints in Merge
Using PATCH endpoints in Merge

How to Update Existing Objects in Merge

Yash Gogri avatar
Written by Yash Gogri
Updated over a week ago

Here's how you can leverage Merge's PATCH endpoints to update objects such a Tickets, CRM Opportunities, and ATS Applications!

Below is an example of how to use the PATCH/Tickets endpoint.

  • To add/change any non-array field (ie.: string, date, number, Merge relation), simply add it in!

{ "model": { "name": "I want to change name", "parent_ticket": "75b33d04-30d2-4f3e-be45-27838bc94342", "due_date": "2022-02-02T00:00:00Z" }
  • To remove any non-array field, use null.

{ "model": { "name": null, "parent_ticket": null, "due_date": null }
  • To modify items in any array fields, enter what you want the output to be. So for example, if I want only tag1 and tag2 but don’t want tag3 in a Ticket’s tags, this is what I would send in the Merge PATCH request:

{ "model": { "tags": ["tag1", "tag2"] }

We handle all the complex logic to add/remove tags for you!

  • To remove all items in an array field, use [].

If you have any questions, please feel free to reach out over Intercom!

Did this answer your question?