Ticket

Merge multiple tickets into one

Merges ticketsToMergeIds into a target ticket and returns the resulting main ticket. targetTicketId is required unless shouldCreateNewTicket is true, in which case a fresh main ticket is created (and an existing target ticket, if given, is archived too). Merged tickets are archived and linked to the main ticket. shouldMergeTasks re-parents linked sub-tickets; shouldMergeContacts merges the contacts of the merged tickets.

PUT

https://api.gleap.io/v3/tickets/merge

Authorizations

Authorizationstring · headerrequired

Bearer authentication header of the form Bearer <token>.

Headers

projectstringrequired

Bodyapplication/jsonrequired

shouldMergeContactsbooleanrequired

shouldMergeTasksbooleanrequired

shouldCreateNewTicketbooleanrequired

ticketsToMergeIdsstring[]required

targetTicketIdstring

Response

application/json

Updated November 1, 2026

curl --request PUT \
  --url https://api.gleap.io/v3/tickets/merge \
  --header 'Authorization: Bearer <token>' \
  --header 'project: <project>' \
  --header 'Content-Type: application/json' \
  --data '{
  "shouldMergeContacts": true,
  "shouldMergeTasks": true,
  "shouldCreateNewTicket": true,
  "ticketsToMergeIds": [
    "<ticketsToMergeIds>"
  ]
}'

No example in the spec.