docs: document EVENT_TYPE_LANGUAGE_CHANGED messaging event#508
Open
mintlify[bot] wants to merge 1 commit into
Open
docs: document EVENT_TYPE_LANGUAGE_CHANGED messaging event#508mintlify[bot] wants to merge 1 commit into
mintlify[bot] wants to merge 1 commit into
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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.
Summary
Documents the new
EVENT_TYPE_LANGUAGE_CHANGEDserver event that messaging API clients now receive over the WebSocket when the PolyAI agent detects a conversation language switch.Changes
EVENT_TYPE_LANGUAGE_CHANGEDsection to the System events list on the Server events reference page, including the payload shape, field description (BCP-47language_code), and a note that the event is journaled, replayed on reconnect, and idempotent.Context
Upstream change added a first-class
LANGUAGE_CHANGEDevent so v2 messaging clients can react to language switches (previously only the new language code was persisted server-side). Clients now see a new event type on the WebSocket and need reference docs to consume it.