Add /fin/escalate endpoint to Preview spec#553
Open
mckenna wants to merge 3 commits into
Open
Conversation
Documents the shipped POST /fin/escalate endpoint (Preview): request/response schema, the escalated reason emitted via the API, and the escalate capability type. Mirrors the developer-docs spec. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Mirrors developer-docs review feedback: the `message` field is visible to the end-user, unlike the internal-only `context`. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Aligns the context param description with the guide's security note. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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
POST /fin/escalateendpoint has shipped on the Preview API version but was missing from this spec. Adding it keeps the spec in sync with developer-docs and generates the endpoint in the SDKs.How?
Adds the
/fin/escalatepath (request/response schema, examples) to the Preview spec, documents theEscalation requested via APIreason on the escalated event, and listsescalateas a capability type. By default an escalation summarises the agent conversation into an internal note and opens a new Helpdesk conversation; an escalation Operator Workflow can override that default.Generated with Claude Code