# CRM to-dos

Create and update activities of provider `CRM_TODO` here. Read and list them through [CRM activities](./activities.md): use `GET /v1/activities/:id` or filter the list by `providerId=CRM_TODO`.

Scope: `crm`. Writes require a key with write access. Activity responses have the same shape as `GET /v1/activities/:id`.

## Operations

- [Create a to-do](./activity-todos/create.md) — `POST /v1/activity-todos`
- [Update a to-do](./activity-todos/update.md) — `PATCH /v1/activity-todos/:id`

## Bitrix24 method selected for PATCH

| Request fields | Bitrix24 method |
|---|---|
| Only `deadline` | `crm.activity.todo.updateDeadline` |
| Only `description` | `crm.activity.todo.updateDescription` |
| Only `responsibleId` | `crm.activity.todo.updateResponsibleUser` |
| Any other combination without `colorId` | `crm.activity.todo.update` with omitted fields preserved |

A full update preserves existing reminders, files, and activity blocks. Set color when creating a to-do; PATCH with a valid `colorId` returns 422 because Bitrix24 full update could erase settings added concurrently. A color outside the palette returns 400. A completed to-do cannot be changed and returns 422.