---
title: "Move or rank a ticket"
method: PATCH
path: "/api/v1/board/tickets/{key}/move"
---

# Move or rank a ticket

`PATCH /api/v1/board/tickets/{key}/move`

## Request

- Base URL: `https://tallymeter.com`
- URL: `https://tallymeter.com/api/v1/board/tickets/{key}/move`
- Auth: HTTP bearer

Moves a ticket to a column and/or places it in that column's order. `above` names the ticket it should sit on top of — how a column is actually ranked — and must be in the target column. The resulting `column_order` is read back, because a rank that silently no-ops is the classic failure. Requires the `board:write` scope.

## Path parameters

- `key` string, required

## Request body

- object
  - `column` string: target column; omit to rank within the current one
  - `above` string: ticket key this one goes directly above
  - `index` integer: absolute 0-based position; ignored when `above` is given

## Response `200`

Moved, with the resulting column order

- object
  - `key` string
  - `column` string
  - `position` integer
  - `column_order` string[]

## Other responses

- `401`: Missing or invalid token
- `403`: Token lacks the required scope, or the account has no active plan
- `404`: No such ticket in this workspace
- `422`: Unknown column, or `above` is in a different column

---

[API](https://skmtc.dev/tallymeter/apis/tallymeter-api.md) · [All operations](https://skmtc.dev/tallymeter/apis/tallymeter-api/llms.txt) · [OpenAPI document](https://skmtc.dev/tallymeter/apis/tallymeter-api/revisions/50044367b64e?raw)