Delete namespace (cascade)
DELETE
/v1/ns/{nsid}
const url = 'https://example.com/v1/ns/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0';const options = { method: 'DELETE', headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'}, body: '{"confirm_id":"example","confirm_timestamp":1}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request DELETE \ --url https://example.com/v1/ns/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0 \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "confirm_id": "example", "confirm_timestamp": 1 }'Requires confirmation body with confirm_id (nsid string) and
confirm_timestamp (unix int). Live calls anywhere in the subtree
normally block the cascade with 409; pass ?force=true (or
X-Force: true) to bypass that guard and flush the stuck
in-progress call rows as part of the purge.
Debug-only: force exists for removing a broken namespace whose
call-tracking rows are stuck. Those rows normally TTL out on their
own. The confirmation body is still required with force.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”nsid
required
string format: uuid
Namespace UUID
Query Parameters
Section titled “Query Parameters”force
boolean
Bypass the live-call guard and flush stuck in-progress call rows (debug-only).
Request Bodyrequired
Section titled “Request Bodyrequired”Media typeapplication/json
object
confirm_id
string
confirm_timestamp
integer
Examplegenerated
{ "confirm_id": "example", "confirm_timestamp": 1}Responses
Section titled “Responses”Deleted
Media typeapplication/json
object
success
required
boolean
Example
{ "success": true}Impact preview (no confirmation supplied)
Media typeapplication/problem+json
RFC 7807 Problem Details
object
type
Problem type slug URI
string
title
string
status
integer
detail
string
key
additional properties
any
Examplegenerated
{ "type": "example", "title": "example", "status": 1, "detail": "example"}default
Section titled “default”Error response
Media typeapplication/problem+json
RFC 7807 Problem Details
object
type
Problem type slug URI
string
title
string
status
integer
detail
string
key
additional properties
any
Examplegenerated
{ "type": "example", "title": "example", "status": 1, "detail": "example"}