Delete trust

Removes one record from a section of your organization's trust centre.

DELETE /v1/trust/{kind}/{id}

Trust → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/trust/{kind}/{id}`
Method	`DELETE`
Operation	`delete_trust_by_kind_by_id`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Removes one record from a section of your organization's trust centre. A record that is not there is a 404, never a silent success. A control that belongs to the deployment's own inventory is removed by a commit, not by a request.

Request

2 fields.

Field	In	Type	Required	Description
`kind`	path	string	yes	Kind is the section — profile, control, document, subprocessor, policy, faq, update or risk.
`id`	path	string	yes	ID is the record's id within that section.

Response

Status	Body	Meaning
`200`	trust.dropped	ok
`default`	problem-details	refused

200 body — 3 fields.

Field	In	Type	Always	Description
`deleted`	body	boolean	—	Deleted is always true; a record that was not there is a 404 instead.
`id`	body	string	—	ID is the record removed.
`kind`	body	string	—	Kind is the section.

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo trust kind rm <kind> <id>

.ts

.py

.go

.rs

.java

import { Configuration, TrustApi } from 'hanzoai';

const api = new TrustApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.deleteTrustByKindById({ kind: 'kind', id: 'id' });

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

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = TrustApi(client).delete_trust_by_kind_by_id(kind='kind', id='id')

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

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

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

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

let result = trust_api::delete_trust_by_kind_by_id(&cfg, Default::default()).await?;

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

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

var result = new TrustApi(client).deleteTrustByKindById();

curl -X DELETE https://api.hanzo.ai/v1/trust/<kind>/<id> \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches trust through the trust tool, which names its 17 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_trusts"
         }
       }
     }'

Trust API · All Hanzo APIs · Interactive reference

Was this page useful?

PreviousList treasury NextGet controls