Get tombstones

Returns what holds a deleted organization's name: when it was deleted and who founded it.

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

Addresshttps://api.hanzo.ai/v1/iam/organizations/tombstones/{owner}/{name}
MethodGET
OperationgetOrganizationTombstone
AuthAuthorization: Bearer $HANZO_API_KEY

Returns what holds a deleted organization's name: when it was deleted and who founded it. A SuperAdmin reads it before deciding to release the name.

Request

2 fields.

FieldInTypeRequiredDescription
ownerpathstringyes
namepathstringyes

Response

StatusBodyMeaning
200iam.Tombstoneok
202Approvalheld for approval
defaultproblem-detailsrefused

200 body — 8 fields.

FieldInTypeAlwaysDescription
createdAtbodystring (date-time)—
createdTimebodystring—
deletedbodyboolean—
founderbodystring—Founder carries the deleted org's founder, so an org counted against its founder's cap stays counted after it is deleted.
idbodystring—
namebodystring—the organization's name
ownerbodystring—the admin registry, as for organizations
updatedAtbodystring (date-time)—

Failure carries the platform error shape — see Errors.

Examples

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

import { Configuration, IamApi } from 'hanzoai';

const api = new IamApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getOrganizationTombstone({ 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).get_organization_tombstone(owner='owner', name='name')
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.IamAPI.GetOrganizationTombstone(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::get_organization_tombstone(&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).getOrganizationTombstone();
curl 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?