---
title: "Reorder project columns"
method: PUT
path: "/companies/{company}/projects/{project}/columns/reorder"
tags: ["Projects"]
---

# Reorder project columns

`PUT /companies/{company}/projects/{project}/columns/reorder`

## Request

- Base URL: `https://api.factuarea.com/v1`
- URL: `https://api.factuarea.com/v1/companies/{company}/projects/{project}/columns/reorder`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-API-Key`

Set the board order of the project columns by sending all their ids in `column_ids`, in the new order. The list must contain every column of the project exactly once; an unknown column returns 404 `project_column_not_found`.

## Path parameters

- `company` string, uuid, required
- `project` string, uuid, required

## Headers

- `Idempotency-Key` string
- `Factuarea-Version` string, date

## Request body

- ReorderProjectColumnsV1Request
  - `column_ids` string[], required: `id` of ALL the columns of the project, in the desired order.

## Response `200`

- ProjectColumnList: Page of columns (the whole board, never more than one page) (`{ data, has_more, next_cursor }`).
  - `data` ProjectColumn[], required
    - `id` string, uuid, required: UUID v7 of the column.
    - `object` 'project_column', required: Stripe-like discriminator. Always `project_column` for this resource.
    - `project_id` string, uuid, required: UUID of the project the column belongs to.
    - `name` string, required: Column name.
    - `slug` string, required: Stable identifier derived from the name, unique in the project (`planned` and `archived` are reserved).
    - `icon` string, nullable, required: Icon of the column, or `null`.
    - `color` string, nullable, required: Color of the column from the task palette, or `null`.
    - `is_final` boolean, required: `true` when moving a task here completes it.
    - `position` integer, required: Position of the column on the board.
  - `has_more` boolean, required: `true` when there are more objects after this page.
  - `next_cursor` string, nullable, required: Value to pass as `starting_after` to get the next page (the `id` of the last object), or `null` when `has_more` is `false`.

## Other responses

- `400`: `parameter_unknown` with `subcode` `retired_active_profile_header`: the retired `X-Active-Profile` header was sent; the company goes in the path. `parameter_invalid_format` on `Factuarea-Version`: the header is not a `YYYY-MM-DD` date. `unsupported_api_version`: the `Factuarea-Version` date is not a supported version.
- `401`: Missing or invalid API key.
- `403`: The request is authenticated but not allowed: the API key lacks the required scope (`insufficient_scope`), the plan does not include the public API or this feature (`addon_not_active`, `feature_not_available_in_plan`), or the module is not available with a test key (`module_not_available_in_sandbox`).
- `404`: The requested resource does not exist or belongs to another company.
- `409`: The request conflicts with data that already exists or with a request running at the same time. `column_has_tasks`: the column still holds tasks. Move them to another column (`move_to_column_id`) before deleting it. `column_slug_in_use`: another column of the project already has that name (or one that produces the same identifier). Choose another name. `project_key_in_use`: another project of the company already uses that `key`. Choose another one.
- `422`: Validation failed. The `error.param` field identifies which input is invalid.
- `429`: Rate limit exceeded. Retry after the duration in `Retry-After`.
- `500`: Unexpected server error.

---

[API](https://skmtc.dev/factuarea/apis/factuarea-public-api.md) · [All operations](https://skmtc.dev/factuarea/apis/factuarea-public-api/llms.txt) · [OpenAPI document](https://skmtc.dev/factuarea/apis/factuarea-public-api/revisions/718e77934422?raw)