Update an escalation destination
Partial update — an omitted field is left unchanged. Changing endpointUrl re-validates it (https + SSRF) and resets status to unverified — the new endpoint must re-pass the handshake test before it can route live. Note status can only be set to disabled or unverified here; a destination reaches active ONLY via testEscalationDestination, never a direct PATCH.
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-destination id (from listEscalationDestinations / createEscalationDestination).
Body
A partial update — an omitted field is left unchanged. Changing endpointUrl resets status to unverified.
chat, sms general, sales, support, billing, scheduling disabled, unverified