/conversations/{id}/mergeMerge a conversation into another conversation
Merges a secondary conversation into a primary conversation, closing the secondary and linking it to the surviving primary thread. Supply the secondary conversation ID in the path and the primary conversation ID in merge_into_conversation_id; the merge requires write_conversations, and also write_tickets when the secondary conversation is a ticket. The response contains the primary conversation.
- IdempotentThe SDK sends
Idempotency-Key, so a retried request is only applied once.
Payload identifying the primary conversation that will survive the merge.
One documented failure
parameter_invalidmerge_into_conversation_id must be a valid integer conversation ID
One documented failure
token_unauthorizedNot authorized to access resource
One documented failure
forbiddenForbidden request
One documented failure
merge_failedPrimary conversation not found
A 400 indicates invalid merge input, a 401 indicates missing or invalid authentication, and a 403 indicates insufficient permissions; merging requires write_conversations, plus write_tickets when the secondary is a ticket. A 422 indicates that the merge failed. The id path parameter must identify the secondary conversation, and merge_into_conversation_id must identify the primary conversation.