Deletes the caller org's OWN starter kit.
Deletes the caller org's OWN starter kit.
DELETE /v1/template/{slug}
| Address | https://api.hanzo.ai/v1/template/{slug} |
| Method | DELETE |
| Operation | delete_template_by_slug |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Deletes the caller org's OWN starter kit. A slug they do not own is a 404, never a delete: the DELETE binds org.
Request
1 field.
| Field | In | Type | Required | Description |
|---|---|---|---|---|
slug | path | string | yes | Slug is the starter kit to act on, from the path. |
Response
| Status | Body | Meaning |
|---|---|---|
204 | — | no content |
Failure carries the platform error shape — see Errors.
Examples
hanzo templates rm <slug>import { Configuration, TemplateApi } from 'hanzoai';
const api = new TemplateApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.deleteTemplateBySlug({ slug: 'slug' });from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import TemplateApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = TemplateApi(client).delete_template_by_slug(slug='slug')cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.TemplateAPI.DeleteTemplateBySlug(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::apis::{configuration::Configuration, template_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = template_api::delete_template_by_slug(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.TemplateApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new TemplateApi(client).deleteTemplateBySlug();The method above is the one at the current release of the document. [email protected] (npm) and [email protected] (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. SDKs →
curl -X DELETE https://api.hanzo.ai/v1/template/<slug> \
-H "Authorization: Bearer $HANZO_API_KEY"The door reaches template through the templates tool, which names its 5 operations with its own verbs — this one among them, under a name only the door 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_templates"
}
}
}'How is this guide?