Cancel outbound DTMF sequence
Rate limit: Per command · Burst: 20 · Refill: 20 req/s
Cancel the active outbound DTMF sequence for the session. Before returning 202, the platform deletes the remaining sequence plan so that it cannot schedule another key or wait action. A key whose transmission has already started might still finish.
If no sequence is active, the platform accepts the request without taking further action. The 202 response acknowledges the cancellation request. The platform does not emit a terminal webhook.
See Keypad input lifecycle events for complete payload schemas and examples.
Authentication
Send Authorization: Bearer <app_uuid>:<api_key> using an active API key. See Authentication for details.
Path parameters
Session identifier.
Headers
optional client-supplied lowercase RFC-4122 v4 UUID returned as operation_uuid; platform generates one when omitted; correlation metadata distinct from Idempotency-Key.
Response headers
Server-owned W3C Trace Context for correlating this response with support and observability data. It is present on successful and error responses. A valid incoming traceparent is linked to, but never becomes, the server-owned trace identifier.