Cancel a Click2Call call

Hangs the call up, whatever leg it has reached — before anyone answered, or mid-conversation. The response is 204 No Content with an empty body.

Repeating the cancel is safe

A repeated DELETE also answers 204. The request is recorded once and every repeat gets the same answer, so a client that retries on a timeout cannot get a spurious failure. Do not read a second 204 as "there was still a call to hang up".

What the cancel shows up as

A cancel that actually ended the call reads back with reason canceled. Its state is completed if the two legs had already been bridged, and failed if the call was hung up before it came together.

If the call had already ended on its own before your DELETE arrived, its original reason is kept — a call nobody answered still reads no_answer. Cleaning up with a defensive DELETE therefore cannot hide why a call ended.

404

404 call_not_found means the call is unknown to you: it never existed, the ID is malformed, it belongs to another account, or it is older than the 12-hour retention window — which runs from when the call was placed, not from when it ended. The cases are deliberately indistinguishable.

See also: click2call_show, which reads the call back after the cancel.