Delete a workflow
Cascades to the workflow's revisions, its state rows and its run log — they are reachable only through it. The delete is a tombstone; a repeat is `404`, not a second `204`.
Cascades to the workflow's revisions, its state rows and its run log — they are reachable only
through it. The delete is a tombstone; a repeat is 404, not a second 204.
Authorization
api_key workflows:writeAn atk_-prefixed API key, created under Settings → API keys.
In: header
Scope: workflows:write
Path Parameters
Workflow id
uuidResponse Body
application/json
application/json
curl -X DELETE "https://example.com/v1/workflows/497f6eca-6276-4993-bfeb-53cbbbba6f08"Get a workflow GET
이전
Patch a workflow's input state PATCH
A merge patch against the shared `input` half: keys absent from the body keep their value, keys set to `null` are removed. Only paths the current revision's contract declares are writable (`input.scratch` is always free-form), so an undeclared path is a `400` naming it and leaves state untouched. `version` is the `input` version the caller read from `GET /v1/workflows/{id}/state` — it says which state the patch was composed against. Because `input` is patched per path, a version that has moved on since does not throw the write away: the store re-reads and re-applies the patch against the live value, so a rival's edit to another path survives rather than being overwritten. Only a write that loses every one of those compare-and-swap retries is refused with `409`, which is a signal about contention, not about a stale read.