Delete Bridge
Telephony & Bridges
Delete Bridge
Permanently delete a telephony bridge
DELETE
Delete Bridge
Documentation Index
Fetch the complete documentation index at: https://docs.unpod.dev/llms.txt
Use this file to discover all available pages before exploring further.
Delete Bridge
Permanently delete a telephony bridge by its slug. Once deleted, the bridge and all associated configurations are removed. This action cannot be undone.Prerequisites: Make sure you have your API Token and Org-Handle ready. See Authentication for details.
Path Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| slug | string | Yes | Unique bridge slug |
You can get the bridge
slug by hitting the Get All Bridges API. The slug field in the response is your Bridge Slug.Headers
| Name | Type | Required | Description |
|---|---|---|---|
| Authorization | string | Yes | API Key format: Token <token> |
| Org-Handle | string | Yes | Organization domain handle |
Common Error Codes
| Status Code | Description |
|---|---|
| 204 | No Content - Bridge deleted successfully |
| 401 | Unauthorized - Invalid or missing API token |
| 403 | Forbidden - Invalid organization handle |
| 404 | Not Found - Bridge not found |
| 500 | Internal Server Error - Server-side error |
Code Examples
Best Practices
- Disconnect First: Always disconnect the provider from the bridge before deleting it
- Irreversible: Deletion is permanent — verify the correct
slugbefore proceeding - 204 Response: A successful delete returns HTTP 204 with no body — handle this in your code
- Error Handling: Handle 404 gracefully — the bridge may have already been deleted
- Pre-check: Use Get Bridge by Slug to verify the bridge exists and check for active numbers before deletion
- Security: Keep API tokens secure and rotate them regularly