[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Merge tickets

> Merge one ticket into another and close the source ticket. Inputs, cURL, Python and Node.js examples and an example response.

Source: https://cotlet.dev/docs/api/zendesk/merge_tickets

Docs sections: [Get started](https://cotlet.dev/docs.md) · [REST API](https://cotlet.dev/docs/api.md) · [MCP](https://cotlet.dev/docs/mcp.md) · [SDKs & CLI](https://cotlet.dev/docs/sdks.md) · [Integrations](https://cotlet.dev/docs/integrations.md)

Merge one ticket into another and close the source ticket.

Zendesk API: https://cotlet.dev/docs/api/zendesk.md

`POST https://cotlet.dev/api/v1/zendesk/target-tickets/{target_ticket_id}/tickets/merge`

Access: write. Confirm: waits for the user's OK before it runs.

Merges the source ticket into the target ticket. A merge is permanent and cannot be undone. Both tickets must be below solved, but you can merge into a solved target without reopening it. The source's most recent public comment is carried to the target with a link, other comments are not, and fields such as tags and priority are not carried over. The source is closed and gets the tag closed_by_merge. Without CCs enabled in your Zendesk, both tickets must have the same requester. By default you confirm each call; you can switch that off for this tool.

## Parameters

| Name | Type | Required | Description |
|---|---|---|---|
| `target_ticket_id` | integer | yes | Ticket that stays open and receives the merge. |
| `source_ticket_id` | integer | yes | Ticket that is closed by the merge. |

## Request

**cURL**

```bash
curl -X POST https://cotlet.dev/api/v1/zendesk/target-tickets/1/tickets/merge \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"source_ticket_id":1}'
```

**Python**

```python
result = client.call("zendesk", "merge_tickets", {"target_ticket_id":1,"source_ticket_id":1})
```

**Node.js**

```js
const result = await cotlet.call('zendesk', 'merge_tickets', {"target_ticket_id":1,"source_ticket_id":1});
```

**CLI**

```bash
cotlet call zendesk merge_tickets --data '{"target_ticket_id":1,"source_ticket_id":1}'
```

## Example response

```json
{
  "target_ticket_id": 48102,
  "source_ticket_id": 48260,
  "source_status": "closed",
  "source_tags": [
    "closed_by_merge"
  ]
}
```

Previous: [Apply macro](https://cotlet.dev/docs/api/zendesk/apply_macro.md)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.