---
title: "Create a task label"
method: POST
path: "/companies/{company}/task-labels"
tags: ["Task Labels"]
---

# Create a task label

`POST /companies/{company}/task-labels`

## Request

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

Add a label to the catalog with a `name` (unique in your company, case-insensitive: 409 `task_label_name_in_use`) and a `color` from the task palette.

## Path parameters

- `company` string, uuid, required

## Headers

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

## Request body

- CreateTaskLabelV1Request
  - `name` string, required: Label name, unique within the company ignoring case (1-60 characters).
  - `color` string, required: Palette key or hexadecimal `#RGB`/`#RRGGBB`.

## Response `201`

Task label created successfully. The `Location` header contains the canonical URL of the newly created label.

- object
  - `data` TaskLabel, required: A label of the task label catalog of your company.
    - `id` string, uuid, required: UUID v7 of the label.
    - `object` 'task_label', required: Stripe-like discriminator. Always `task_label` for this resource.
    - `name` string, required: Label name, unique in your company (case-insensitive).
    - `color` string, required: Color from the task palette.
    - `tasks_count` integer, required: Tasks of your company that carry the label, archived tasks included.
    - `created_at` string, date-time, required: Creation timestamp.
    - `updated_at` string, date-time, required: Last update timestamp.

## 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).
- `409`: The request conflicts with data that already exists or with a request running at the same time. `task_label_name_in_use`: the company already has a label with that name. Use the existing one or choose another name. `resource_conflict`: another request was reserving identifiers for the same kind of record at that moment and this one could not complete its reservation. Nothing was written; send the request again after a few seconds.
- `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)