Remove company_id from conversation response schema#390
Merged
Conversation
Enhance the description to clarify that: - Deletion is permanent and cannot be reversed - All sensitive data is removed (replies, attributes, uploads) - Conversation still appears in reporting with incomplete data This provides better clarity for API consumers about the implications of deleting conversations. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
The company_id field is not returned by the API in conversation responses, so it should not be in the conversation schema. Note: company_id in update_conversation_request schema is preserved as it is correctly used in PUT request bodies.
junaid-zaidi-intercom
approved these changes
Mar 3, 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.
http://github.com/intercom/intercom/issues/453311
Summary
Removes the
company_idfield from the conversation response schema across API versions 2.14, 2.15, and Unstable. This field is not actually returned by the API in conversation GET responses, so it should not be documented in the schema.Changes
company_idfrom conversation schema in:descriptions/2.14/api.intercom.io.yamldescriptions/2.15/api.intercom.io.yamldescriptions/0/api.intercom.io.yaml(Unstable)What's NOT Changed
company_idfield inupdate_conversation_requestschema is preserved as it is correctly used in PUT request bodies to update company associationscompanyfield (object reference) in conversation schema remains unchangedImpact
company_idin the Conversation response typeValidation
✅
fern checkpassed with 0 errors✅ All YAML files remain valid
✅ Adjacent fields (team_assignee_id, company, tags) intact
Related
Companion PR in developer-docs: http://github.com/intercom/developer-docs/pull/752