Document call_summary event_details (call_id) on the Preview spec - #615
Merged
Conversation
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
VarshSuresh
approved these changes
Aug 5, 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
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.
What changed
Documents the
call_summaryvariant ofevent_detailson conversation parts, added by intercom/intercom#552808 (issue intercom/intercom#552202).A phone conversation can contain several calls, and therefore several
call_summaryparts side by side. Nothing in the API said which call each summary described — integrators were reduced to matchingcall.initiated_atagainst the nearestcall_summary.created_at. The monolith PR exposes the call id on the part:The id matches the
idreturned by the Calls API and by thecall.started,call.ended,call.recording_availableandcall.transcription_availablewebhook topics, so it is a direct join key.Spec changes:
call_summaryschema incomponents/schemas, following the existingPart type - <part_type>convention used byconversation_tags_updated,snoozed,priority_changedand the SLA variantsevent_detailsanyOfNo inline response examples needed updating: this adds a variant to the
anyOfrather than a field toconversation_part, and none of the existing part examples arecall_summaryparts.Which API versions are affected
Preview (
descriptions/0/api.intercom.io.yaml) only. The monolith change is registered on the unstable/preview version, so it is not visible on any pinned stable version yet.Validation
fern checkreports the same 3 errors and 300 warnings before and after this change (all pre-existing, inpreview/conversationsAttributes.ymlandpreview/articles.yml) — this change introduces none.Generated with Claude Code