Hanzo

Delete

Delete — 2 operations on https://api.hanzo.ai.

The REST reference for Delete — 2 operations, generated from the OpenAPI document.

Base URLhttps://api.hanzo.ai
Operations2
AuthAuthorization: Bearer $HANZO_API_KEY

tasks

DELETE /tasks/{wildcard1}

The tasks console's assets and client-side routes

Serves the console's static assets on GET, and returns the application shell for any path that is not a file — client-side routing means a deep link into the console is a shell load, not a 404.

A path that looks like a missing asset therefore answers 200 with HTML rather than 404; look at the content type, not the status, when a resource seems to be missing.

This is the task console itself — HTML and hashed assets, not an API. Only GET and HEAD are served; every other method is refused 405. Hashed assets are returned immutable and cached for a year, while the shell is always revalidated, so a new deployment replaces a stale console on the next request.

ParameterInTypeRequiredDescription
wildcard1pathstringyes

DELETE /tasks

The tasks console

Serves the console's application shell on GET, which is the entry point a browser loads before it calls anything under /v1/tasks/.

This is the task console itself — HTML and hashed assets, not an API. Only GET and HEAD are served; every other method is refused 405. Hashed assets are returned immutable and cached for a year, while the shell is always revalidated, so a new deployment replaces a stale console on the next request.


All Hanzo APIs · Interactive reference

How is this guide?

On this page