Delete workflows

Deletes one of the caller's workflows and its runs.

DELETE /v1/flow/workflows/{workflow}

Addresshttps://api.hanzo.ai/v1/flow/workflows/{workflow}
MethodDELETE
Operationdelete_flow_workflows_by_workflow
AuthAuthorization: Bearer $HANZO_API_KEY

Deletes one of the caller's workflows and its runs. Ownership is verified first; a foreign id answers 404 and deletes nothing.

Request

1 field.

FieldInTypeRequiredDescription
workflowpathstringyesWorkflow is the workflow's UUID, taken from the path.

Response

StatusBodyMeaning
200ok
defaultproblem-detailsrefused

200 body — 1 field.

FieldInTypeAlwaysDescription
(body)bodyanyyes

Failure carries the platform error shape — see Errors.

Examples

hanzo flow workflows rm <workflow>
import { Configuration, FlowApi } from 'hanzoai';

const api = new FlowApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.deleteFlowWorkflowsByWorkflow({ workflow: 'workflow' });
from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import FlowApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = FlowApi(client).delete_flow_workflows_by_workflow(workflow='workflow')
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.FlowAPI.DeleteFlowWorkflowsByWorkflow(context.Background()).Execute()
if err != nil {
	return err
}
use hanzo_client::apis::{configuration::Configuration, flow_api};

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

let result = flow_api::delete_flow_workflows_by_workflow(&cfg, Default::default()).await?;
import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.FlowApi;

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

var result = new FlowApi(client).deleteFlowWorkflowsByWorkflow();
curl -X DELETE https://api.hanzo.ai/v1/flow/workflows/<workflow> \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches flow through the flow tool, which names its 8 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_flow_runs"
         }
       }
     }'

Flow API · All Hanzo APIs · Interactive reference

Was this page useful?