Fix: Remove conversation_to_link_id from 2.14 version documentation #308
Conversation
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
🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
VarshSuresh
changed the title
davymalone
approved these changes
Sep 19, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
conversation_to_link_idfield from 2.14 API specificationProblem
The
conversation_to_link_idfeature for linking tickets to conversations is only available in the Unstable API version. However, it was incorrectly documented in the 2.14 version, causing confusion for customers trying to use this feature in the stable version. There has been same confusion previously as well.Solution
Removed the
conversation_to_link_idfield definition from:docs/references/@2.14/rest-api/api.intercom.io.yaml(lines 17902-17910)🤖 Generated with Claude Code