agency-board

POST `/v1/agency/boards/{boardId}/columns/{columnId}/move`

Reorder a column in the board's strip.

Authentication

Send an API key as a bearer token. This endpoint does not state a specific permission in the specification, so give your key the least it needs and check the response rather than assuming.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X POST https://api.zinndigital.com/v1/agency/boards/{boardId}/columns/{columnId}/move \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "position": <integer> }'

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

⛔⛔ A separate operation, because `PATCH` on a column no longer accepts `position` at all. It used to: it wrote the value and shifted no neighbour, so dragging the last column to the front left two columns claiming position 0 and the board fell back to `created_at` order — the write succeeded, the response was 200, and the column appeared not to have moved. This opens a gap and reindexes the strip, exactly as a card move does. ⭐ It returns the WHOLE strip rather than the moved column: a reorder renumbers every neighbour, so a response carrying one column would leave the caller holding stale positions for the rest.

Parameters

Name	Type	Required	What it is
`boardId (path)`	`Uuid`	Yes	Project board ID (UUIDv7).
`columnId (path)`	`Uuid`	Yes	Board column ID (UUIDv7).

Request body

Name	Type	Required	What it is
`position`	`integer`	Yes	—

Response

Name	Type	Required	What it is
`items`	`AgencyBoardColumn[]`	Yes	—

Errors this endpoint can return

401 · 403 · 404 · 422

POST /v1/agency/boards/{boardId}/columns/{columnId}/move