Add POST /conversations/{id}/merge endpoint#503
Merged
Conversation
faizzed
approved these changes
May 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why?
A new endpoint for merging conversations has been added to the REST API. This PR adds the corresponding OpenAPI spec so SDK consumers and developers can discover and use it.
How?
Adds the
POST /conversations/{id}/mergepath andmerge_conversations_requestschema to the Preview spec, plus a Fern type name override in the preview overrides file. The endpoint acceptsmerge_into_conversation_id(the target conversation) in the request body and returns the primary conversation on success. Error responses cover 400 (invalid parameter), 401 (unauthorized), 403 (forbidden), and 422 (merge failed — primary not found, already merged, self-merge).Generated with Claude Code