Claim an escalation
Claim a requested/notified escalation, setting a per-channel activity-based lease. Idempotent for the SAME key (re-claim extends the lease); a claim by a DIFFERENT key returns 409 claim_conflict. The claim preconditions are revalidated at claim time: the destination’s AI-Harness integration must still be connected and — unless the session is a handshake test — the destination must still be active, else 409 destination_unavailable (the pre-claim SLA sweeper still fires the fallback so the visitor is not stranded). The returned contextPackage.transcriptWindow is rebuilt at claim so the claimer starts current with any turns forwarded between requested and claimed. Requires the org to be on a Starter plan or higher.
Authorizations
Flowyte secret API key (Authorization: Bearer flowyte_sk_live_…). Scope-gated; is scoped to your organization — a key can never reach another tenant. The listed scopes in each operation's apiKey requirement are the scopes that key must hold. The tokenUrl is nominal: keys are minted in the dashboard.
Path Parameters
The escalation session id to claim.