Skip to main content
POST
Terminate (hang up) an in-flight outbound call
Back to the Outbound Dialing API overview Hangs up a call that has not yet reached phase=terminal. Drives the call to phase=terminal, outcome=canceled. Don’t use this API on a call that’s already terminal. It returns the call’s existing terminal state, not an error. The request needs the outbound_calls.initiate scope, the same scope as placing a call. The outbound_calls.read scope is not enough. The response returns the outboundCallId, phase, and outcome. A call ID that does not exist, or that belongs to a different project, returns 404.

Authorizations

x-api-key
string
header
required

Project-bound Platform API key (abl_...). The key must carry outbound_calls.initiate for write operations (initiate, terminate) or outbound_calls.read for read operations (lookup, list, summary, search, event stream).

Path Parameters

projectSlug
string
required

The project's slug.

Minimum string length: 1
env
string
required

Deployment environment segment the call runs under, for example, production, staging, dev.

Minimum string length: 1
outboundCallId
string
required

Identifier returned when the call was initiated.

Minimum string length: 1

Response

The call's post-termination state.

success
boolean
required
data
object
required