Delete kv

Deprovisions one Hanzo KV store.

DELETE /v1/provisioning/kv/{name}

Provisioning → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/provisioning/kv/{name}`
Method	`DELETE`
Operation	`delete_provisioning_kv_by_name`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Deprovisions one Hanzo KV store. It reverts any app instance bound to it back to Base BEFORE tearing down the org's dedicated Valkey instance, then deletes the sealed credential and removes the metadata row. Answers 204 with no body; a second call is a 404.

Request

1 field.

Field	In	Type	Required	Description
`name`	path	string	yes	Name is the resource's org-unique slug, from the path.

Response

Status	Body	Meaning
`204`	—	no content
`default`	problem-details	refused

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo provisioning kv rm <name>

.ts

.py

.go

.rs

.java

import { Configuration, ProvisioningApi } from 'hanzoai';

const api = new ProvisioningApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.deleteProvisioningKvByName({ name: 'name' });

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

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = ProvisioningApi(client).delete_provisioning_kv_by_name(name='name')

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

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

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

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

let result = provisioning_api::delete_provisioning_kv_by_name(&cfg, Default::default()).await?;

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

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

var result = new ProvisioningApi(client).deleteProvisioningKvByName();

curl -X DELETE https://api.hanzo.ai/v1/provisioning/kv/<name> \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches provisioning through the provisioning tool, which names its 28 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": "get_provisioning_datastore"
         }
       }
     }'

Provisioning API · All Hanzo APIs · Interactive reference

Was this page useful?

PreviousDelete docdb NextDelete s3