Delete workflow
Answers 307 with Location /v1/workflow/ — this address serves nothing itself.
DELETE /v1/workflow
| Address | https://api.hanzo.ai/v1/workflow |
| Method | DELETE |
| Operation | delete_workflow |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Answers 307 with Location /v1/workflow/ — this address serves nothing itself. The status and the Location are the same on every method; a GET additionally carries the short HTML body a browser falls back to when it does not follow the redirect itself.
A 307 preserves both the method and the body, so a client that follows redirects re-sends the request unchanged to /v1/workflow/ and nothing is lost. A client that does NOT follow redirects sees only the 307 and performs no work — address /v1/workflow/ directly and the hop disappears.
Request
DELETE /v1/workflow takes no parameters and no body — the credential is the whole request.
Response
The document declares no response body for this operation. It answers 200 on success and the platform error shape on failure — see Errors.
Examples
hanzo workflow clearimport { Configuration, WorkflowApi } from 'hanzoai';
const api = new WorkflowApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.deleteWorkflow();from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import WorkflowApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = WorkflowApi(client).delete_workflow()cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)
resp, _, err := client.WorkflowAPI.DeleteWorkflow(context.Background()).Execute()
if err != nil {
return err
}use hanzo_client::apis::{configuration::Configuration, workflow_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = workflow_api::delete_workflow(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.WorkflowApi;
ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));
var result = new WorkflowApi(client).deleteWorkflow();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/workflow \
-H "Authorization: Bearer $HANZO_API_KEY"MCP declares no tool for workflow — tools/list on https://api.hanzo.ai/v1/mcp names the products it does reach. Use HTTP or an SDK.
How is this guide?