VEverdun
speakers

Hang Up Voice Agent

Hang the AI voice agent up and take the incident back.

Same permission and same tenant scoping as the operator's Talk Down, and for the same reason: this is an operations power over real-world sound at a customer site, not a configuration one.

The event id is the ONLY address. There is no call id in the request, so an operator can only ever reach the call belonging to an event their grants already let them open.

404 when no announcement was ever placed; 409 when one was and has already ended; 200 otherwise — including when the device refuses to hang up, which is logged rather than raised (see the response model).

delete/events/{event_id}/voice-agent-call

Request

  • Base URL
    https://api.verdun.ai (the document declares no server; this is the origin it was published from)
  • URL
    https://api.verdun.ai/events/{event_id}/voice-agent-call
  • Auth
    HTTP bearer

Path parameters

event_idstring required

Response

Successful Response

successboolean required

True when the hang-up was requested and recorded. Read device_confirmed to learn whether the speaker has actually stopped.

speaker_labelstring nullable

The speaker the agent was speaking through; null if that speaker has since been retired.

end_reasonstring required

Always operator_hangup on this route.

announced_atstring date-time nullable

When the announcement was confirmed delivered, if it ever was. Null means nothing was confirmed, and the observation was cancelled so the event goes back to the human queue; a value means the deterrent did reach the site and the observation window stands.

device_confirmedboolean required

True when the speaker confirmed it hung the SIP call up. False means the request was recorded but the device did not answer: the call may still be live, the announcement row stays open, and the watchdog keeps retrying — show "hanging up…" rather than "ended".

Example response

{
  "speaker_label": "SE Horn — dumpster",
  "end_reason": "operator_hangup"
}

Changes

No recorded changes to this operation across all 2 revisions of this API.