Repository navigation
Remove the stale top-level ai_topics field from Preview conversations - #738
Merged
Merged
Conversation
Preview returns AI topics inside custom_attributes, not as a separate top-level field, so drop the stale property, its schemas and the example keys. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
cathalging
approved these changes
Oct 21, 2026
cathalging
left a comment
Contributor
There was a problem hiding this comment.
✅ Approve: Preview's conversation schemas now match what the API returns
The API returns AI topics inside custom_attributes (under "AI Topic and Subtopic"), not as a top-level ai_topics field. Removing the field and its three schemas brings Preview in line with that, and nothing else still points at the removed schemas.
Optional follow-up: 2.17 still has one empty ai_topics: key in the /conversations/{id}/merge response example (descriptions/2.17/api.intercom.io.yaml:16055). Worth removing in the follow-up the description mentions.
SDK note: the Preview SDK loses the AiTopics, AiTopic and AiSubtopic types and the Conversation.aiTopics property. Code that names them won't compile, but the API never filled them in, so no data is lost.
~ Automated via Claude
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.
Why?
The Preview spec says a conversation has a top-level
ai_topicsfield and shows it in 16 response examples, but the API doesn't return it. Preview returns AI topics insidecustom_attributesunder "AI Topic and Subtopic", which the spec already describes, so readers and the SDKs expect a field that never arrives.How?
Removes the stale field, its three schemas, which nothing else uses, and the empty example keys from the Preview spec.
Notes for reviewers
AiTopics,AiTopicandAiSubtopictypes go away.fern check: 0 errors.ai_topicskey in a response example. That's left for a follow-up.Generated with Claude Code