Use Cases
- Admin intervention: Manually end calls that need immediate termination
- Automatic cutoff: End calls when certain conditions are met (e.g., time limits, budget caps)
- Emergency stop: Quickly terminate all active calls during system maintenance
- Quality control: End calls that are not meeting quality standards
Path Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
call_sid | string | Yes | The unique call SID (Session ID) from your telephony provider |
Request
This endpoint does not require a request body.Response
Success (200 OK)
| Field | Type | Description |
|---|---|---|
success | boolean | Whether the termination was successful |
message | string | Status message including the provider used |
Error Responses
400 Bad Request
Returned when the call is not in an “ongoing” status.404 Not Found
Returned when the call doesn’t exist or doesn’t belong to your organization.500 Internal Server Error
Returned when the telephony provider fails to terminate the call.Provider Support
This endpoint works with all supported telephony providers:| Provider | Notes |
|---|---|
| Twilio | Uses Twilio’s call update API |
| Telnyx | Uses Telnyx Call Control API |
| Vonage | Uses Vonage Voice API |
| BYO SIP Trunk | Uses SIP CANCEL/BYE signaling |
Examples
Python
Node.js
Terminate All Active Calls
Notes
- The call status will be updated to “completed” in the database after termination
- Call duration is calculated up to the termination time
- Billing is recorded for the portion of the call that occurred
- Termination is immediate - there is no graceful hangup message by default