Vobiz Logo
Vobiz
|API Documentation
Console
← Back to Origination URIs

Delete Origination URI

Permanently remove an origination URI from a trunk.

This API permanently deletes an origination URI from your trunk. Once deleted, the trunk will no longer route outbound calls to this destination. The operation cannot be undone - deleted URIs must be recreated if needed again.

Warning: Deleting an origination URI is permanent and cannot be reversed. Ensure you have at least one active URI remaining for outbound calls to continue functioning.

Important: If you delete all origination URIs, your trunk will not be able to route any outbound calls. Always maintain at least one active URI for production trunks.

Alternative: Instead of deleting, consider setting enabled: falseto temporarily disable the URI without losing the configuration.

This allows you to re-enable the URI later without needing to reconfigure the SIP destination, priority, and weight.

HTTP Request

DELETEhttps://api.vobiz.ai/api/v1/account/{account_id}/origination-uris/{uri_id}

Authentication Required:

  • • X-Auth-ID: Your account ID (e.g., {Auth_ID})
  • • X-Auth-Token: Your account Auth Token
  • • Content-Type: application/json

Response

Returns HTTP 204 No Content on successful deletion. No response body is returned.

Response - 204 No Content
No Content

Examples

cURL - Delete Origination URI

cURL Request
curl -X DELETE https://api.vobiz.ai/api/v1/account/{Auth_ID}/origination-uris/e1f2a3b4-c5d6-7890-efab-567890123456 \
  -H "X-Auth-ID: YOUR_AUTH_ID" \
  -H "X-Auth-Token: YOUR_AUTH_TOKEN"

Error Response (404 Not Found): If the origination URI does not exist:

Error Response - 404 Not Found
{
  "error": "Origination URI not found",
  "code": 404
}

Before Deleting:

  • • List all origination URIs to verify you're deleting the correct one
  • • Ensure at least one other active URI exists for outbound call routing
  • • Consider the impact on failover and load balancing configuration
  • • Save URI configuration details if you might need to recreate it later

Safe Deletion Workflow:

  1. First, set enabled: false on the URI to disable it
  2. Monitor outbound calls to ensure remaining URIs handle traffic correctly
  3. Wait for a testing period (e.g., 24 hours) to confirm no issues
  4. If no problems occur, proceed with permanent deletion
  5. If issues arise, re-enable the URI before it's deleted

Production Best Practices:

  • • Never delete the last remaining active origination URI on a production trunk
  • • Always maintain at least 2 URIs (one primary, one backup) for redundancy
  • • Document the reason for deletion and the URI configuration in your change log
  • • Plan deletions during maintenance windows to minimize potential impact
Update Origination URI