Add reason_code to Finish Conversation#12
Merged
Conversation
The public API PUT /conversations/{id}/finish now accepts an optional
reason_code field alongside the existing free-text reason. Expose it on
FinishConversationParams so callers can categorise why a conversation
finished (e.g. customer-ended-chat, customer-unresponsive).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
gmtuca
approved these changes
Jul 21, 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.
Adds an optional
reason_codefield toFinishConversationParams, so callers ofclient.conversations.finish(id, ...)can categorise why a conversation finished (e.g.customer-ended-chat,customer-unresponsive) in addition to the existing free-textreason. The field is serialized verbatim into the request body under the exact JSON keyreason_code, matching how the SDK already models snake_case wire fields (and thereason_codefield on hand-off webhook events). It is optional, so existing calls compile and behave unchanged. Extends the finish HTTP test to assert bothreasonandreason_codeare sent, and demonstrates the field in the conversations example.Mirrors platform change gradientlabs-ai/wearegradient#30159 and docs gradientlabs-ai/docs#236.
🤖 Generated with Claude Code