---
title: "Bulk update tasks"
method: POST
path: "/companies/{company}/tasks/bulk-update"
tags: ["Tasks"]
---

# Bulk update tasks

`POST /companies/{company}/tasks/bulk-update`

## Request

- Base URL: `https://api.factuarea.com/v1`
- URL: `https://api.factuarea.com/v1/companies/{company}/tasks/bulk-update`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-API-Key`

Apply the same change to up to 200 tasks (`task_ids`): `priority`, `assignee_id` (`null` unassigns), `due_on` (`null` clears it), `add_label_id` and/or `remove_label_id`. A key you do not send is left untouched. Sending no change, or adding and removing the same label, returns 422. Requires an `Idempotency-Key`.

## Path parameters

- `company` string, uuid, required

## Headers

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

## Request body

- BulkUpdateTasksV1Request
  - `task_ids` string[], required
  - `priority` 'none' | 'low' | 'medium' | 'high' | 'urgent': New priority: `none`, `low`, `medium`, `high` or `urgent`.
  - `assignee_id` string, uuid, nullable: `id` of the new assignee, a member of the company; `null` removes the assignee.
  - `due_on` string, date, nullable: New due date (`YYYY-MM-DD`); `null` removes it.
  - `add_label_id` string, uuid: `id` of the label to add.
  - `remove_label_id` string, uuid: `id` of the label to remove.

## Response `200`

- object
  - `data` TaskBulkResult, required: Result of a bulk task operation. Tasks that no longer exist or were moved are skipped silently.
    - `object` 'task_bulk_result', required: Stripe-like discriminator. Always `task_bulk_result` for this resource.
    - `operation` 'status' | 'update' | 'delete', required: Bulk operation performed.
    - `changed` integer, required: Tasks actually changed.

## 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. `profile_not_found`: the company in the path does not exist, is not in the API key scope or belongs to the other environment (live or test).
- `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)