Delete tombstones

Frees the name of a deleted organization so it can be founded again.

DELETE /v1/iam/organizations/tombstones/{owner}/{name}

IAM → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/iam/organizations/tombstones/{owner}/{name}`
Method	`DELETE`
Operation	`releaseOrganizationName`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Frees the name of a deleted organization so it can be founded again. Deleting an organization leaves its name held, because every service keys a tenant by that name; releasing it is a SuperAdmin's decision, recorded on the audit trail, and it is refused while anything IAM keeps is still keyed by the name. Everything else keyed by it across the estate must be purged first.

Request

2 fields.

Field	In	Type	Required	Description
`owner`	path	string	yes
`name`	path	string	yes

Response

Status	Body	Meaning
`200`	iam.ReleaseOutput	ok
`202`	Approval	held for approval
`default`	problem-details	refused

200 body — 1 field.

Field	In	Type	Always	Description
`released`	body	boolean	—

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.

.ts

.py

.go

.rs

.java

import { Configuration, IamApi } from 'hanzoai';

const api = new IamApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.releaseOrganizationName({ owner: 'owner', name: 'name' });

from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import IamApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = IamApi(client).release_organization_name(owner='owner', name='name')

cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.IamAPI.ReleaseOrganizationName(context.Background()).Execute()
if err != nil {
	return err
}

use hanzo_client::apis::{configuration::Configuration, iam_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = iam_api::release_organization_name(&cfg, Default::default()).await?;

import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.IamApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new IamApi(client).releaseOrganizationName();

curl -X DELETE https://api.hanzo.ai/v1/iam/organizations/tombstones/<owner>/<name> \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches iam through the iam tool, which names its 44 operations with its own verbs — this one among them, under a name only MCP declares. describe explains any of them:

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "describe",
         "arguments": {
           "op": "list_iam_applications"
         }
       }
     }'

IAM API · All Hanzo APIs · Interactive reference

Was this page useful?

PreviousReplace workspaces NextCreate avatar