Skip to content

[api] add reason_code to Finish Conversation request#32

Merged
Catchpowle merged 1 commit into
mainfrom
public-api-finish-reason-code
Jul 21, 2026
Merged

[api] add reason_code to Finish Conversation request#32
Catchpowle merged 1 commit into
mainfrom
public-api-finish-reason-code

Conversation

@Catchpowle

Copy link
Copy Markdown
Contributor

Adds an optional reasonCode field to FinishConversationRequest, serialized to the JSON key reason_code, so callers of PUT /conversations/{id}/finish can supply a validated finish reason code (currently customer-ended-chat or customer-unresponsive) alongside the existing free-text reason. It is modelled as a String and mirrors the reason_code convention already used for hand-off events; the field is optional (@JsonInclude(NON_NULL), builder-set), so existing builder usages compile and serialize unchanged.

This mirrors the platform change gradientlabs-ai/wearegradient#30159 and docs gradientlabs-ai/docs#236.

🤖 Generated with Claude Code

Add an optional reason_code field to FinishConversationRequest, mapped to
the JSON key `reason_code`, so callers can set a validated finish reason
code (e.g. customer-ended-chat, customer-unresponsive) alongside the
existing free-text reason. The field is optional, so existing builder
usages compile unchanged.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@Catchpowle
Catchpowle force-pushed the public-api-finish-reason-code branch from b3c4576 to d12f211 Compare July 21, 2026 13:45
@Catchpowle
Catchpowle merged commit 32128e9 into main Jul 21, 2026
1 check passed
@Catchpowle
Catchpowle deleted the public-api-finish-reason-code branch July 21, 2026 13:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants