---
title: "Remove a flow rule"
method: DELETE
path: "/flow-rules/{rule}"
tags: ["Structure"]
---

# Remove a flow rule

`DELETE /flow-rules/{rule}`

## Request

- Base URL: `https://api.yokka.ai/api/v1`
- URL: `https://api.yokka.ai/api/v1/flow-rules/{rule}`
- Auth: HTTP bearer

Delete a flow rule by its id (from get_flow_rules). Cards stay where they are; the event just stops moving or flagging them. To pause a rule instead, update_flow_rule with enabled: false. A rule that starts runs on a runner is removed only in the app, by the runner's owner or an admin.

Needs a token with the `board.manage` permission. Without it: *This token can't change lanes, swimlanes or flow rules. Ask the human to do it, or to create a token with that permission turned on.* Same as the MCP tool `remove_flow_rule`.

## Path parameters

- `rule` string, required: The flow rule's id, from GET /projects/{project}/flow-rules.

## Headers

- `X-Client-Name` string

## Response `200`

The tool's result.

- object
  - `id` string, required

## Other responses

- `400`: The arguments aren't valid, or the change isn't possible as asked.
- `401`: The token is missing, invalid, revoked or expired.
- `403`: The token can't do this, or a plan or board limit was reached.
- `404`: Something it names wasn't found, or isn't visible to this token.
- `413`: The request body is too large.
- `429`: Too many calls: retry after `Retry-After` seconds.

---

[API](https://skmtc.dev/yokka/apis/yokka-rest-api.md) · [All operations](https://skmtc.dev/yokka/apis/yokka-rest-api/llms.txt) · [OpenAPI document](https://skmtc.dev/yokka/apis/yokka-rest-api/revisions/19083353485e?raw)