Delete a flow

DELETE 
/v1/flows/:flow_id

Deletes the flow, every version, every submission collected through it and their stored files, in the background: 202 now, and the flow answers 404 once the job has run, usually within seconds; until then it reads unchanged. There is no undo. A published flow must be unpublished first (409 must_unpublish_first). Requires the flows:write scope, which is therefore a destructive scope: keep keys that hold it as carefully as the data.

Request

Responses

202

Accepted: the deletion is running. No response body. The flow reads unchanged until the job has run, then answers 404.

400

A malformed flow_id (code: invalid_parameter), or an unrecognised query parameter (code: unknown_parameter).

401

Missing, malformed, unknown, revoked, or expired key — one body for all of them (code: unauthorized), with WWW-Authenticate: Bearer realm="hop".

403

The key lacks the scope (code: insufficient_scope), named in WWW-Authenticate: Bearer error="insufficient_scope", scope="…".

404

No such flow — nonexistent, already deleted, or another organisation's.

409

code: must_unpublish_first — the flow has a published version. Unpublish it, then delete.

429

Over a bucket. Obey Retry-After (seconds); RateLimit-* fields are informational.

Response Headers

RateLimit-Limit

Requests allowed in the current window. Informational.

RateLimit-Remaining

Requests left in the current window. Informational.

RateLimit-Reset

Seconds until the window resets. Informational.

Retry-After

Seconds to wait before retrying. The binding contract.