---
title: "Remove a lane"
method: DELETE
path: "/projects/{project}/swimlanes/{swimlane}/lanes/{lane}"
tags: ["Structure"]
---

# Remove a lane

`DELETE /projects/{project}/swimlanes/{swimlane}/lanes/{lane}`

## Request

- Base URL: `https://api.yokka.ai/api/v1`
- URL: `https://api.yokka.ai/api/v1/projects/{project}/swimlanes/{swimlane}/lanes/{lane}`
- Auth: HTTP bearer

Delete a lane. Its cards move to another lane first (any swimlane), and rules that moved cards into it are switched off. A swimlane keeps at least one lane.

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_lane`.

## Path parameters

- `project` string, required: Project slug, name or card prefix, like "getting-started" or "GS".
- `swimlane` string, required: Swimlane name, like "Bugs".
- `lane` string, required: Lane name, like "Ready" or "Backlog".

## Query parameters

- `moveCardsTo` string, required: The lane its cards move to.
- `moveCardsToSwimlane` string: That lane's swimlane. Defaults to the same swimlane.

## Headers

- `X-Client-Name` string

## Response `200`

The tool's result.

- object
  - `lane` string, required
  - `moved` integer, 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)