Correct translated-reply webhook topic descriptions in Preview spec - #638
Merged
Merged
Conversation
The translations field description implied conversation.admin.replied.translated and ticket.admin.replied.translated fire for every translated admin reply. In practice the topic is suppressed when the reply's body has text outside an HTML block element, which includes plain-text replies sent through the REST API. Add that caveat to the three affected schema descriptions in the Preview spec.
VedranZoricic
approved these changes
Aug 26, 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?
The Preview spec's
translationsfield description says it backs theconversation.admin.replied.translatedandticket.admin.replied.translatedwebhook topics, implying they fire for every translated admin reply. Since a gate that shipped 2026-08-24, that's no longer true: the topic is suppressed whenever the reply's body has text outside an HTML block element, which includes every plain-text reply sent through the REST API (which only acceptsbody, neverblocks). A developer who subscribes to either topic and sends a plain-text reply gets nothing back, with no way to tell why from the current docs, even though both topics went GA on 2026-08-26.How?
Add a short caveat to the three affected
translationsdescription blocks explaining when the event is suppressed.Generated with Claude Code