[{"data":1,"prerenderedAt":7},["ShallowReactive",2],{"docs-entities\u002Ftasks\u002Fchecklist\u002Fcreate":3,"docs-tabs-entities\u002Ftasks\u002Fchecklist\u002Fcreate":6},{"content":4,"lastmod":5},"## Add a checklist item\n\n`POST \u002Fv1\u002Ftasks\u002F:taskId\u002Fchecklist`\n\nAdds an item to a task's checklist. `title` is required. Returns the `id` of the new item.\n\n## Parameters\n\n| Parameter | Type | Required | Description |\n|----------|-----|:-----:|---------|\n| `taskId` (path) | integer | yes | Task ID |\n\n## Request fields (body)\n\n| Field | Type | Required | Description |\n|------|-----|:-----:|---------|\n| `title` | string | yes | Item text. With `parentId: 0`, this becomes the name of the new checklist |\n| `sortIndex` | integer | no | Sort index. The smaller the value, the higher the item appears in the list |\n| `isImportant` | boolean \u002F `Y`,`N` | no | Importance flag |\n| `isComplete` | boolean \u002F `Y`,`N` | no | Completion status at creation |\n| `parentId` | integer | no | Parent item ID. `0` creates a new checklist container in the task |\n| `members` | object | no | Item members: `{ \"\u003CuserId>\": { \"type\": \"A\" \\| \"U\" } }`. `A` — participant, `U` — observer. Employee list — [`GET \u002Fv1\u002Fusers`](\u002Fdocs\u002Fentities\u002Fusers) |\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl -X POST \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Ftasks\u002F3943\u002Fchecklist\" \\\n  -H \"X-Api-Key: YOUR_API_KEY\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\n    \"title\": \"Collect and check documents\",\n    \"sortIndex\": 100,\n    \"isImportant\": true\n  }'\n```\n\n### curl — OAuth application\n\n```bash\ncurl -X POST \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Ftasks\u002F3943\u002Fchecklist\" \\\n  -H \"X-Api-Key: YOUR_APP_KEY\" \\\n  -H \"Authorization: Bearer USER_SESSION_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\n    \"title\": \"Collect and check documents\",\n    \"sortIndex\": 100,\n    \"isImportant\": true\n  }'\n```\n\n### JavaScript — personal key\n\n```javascript\nconst res = await fetch(\"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Ftasks\u002F3943\u002Fchecklist\", {\n  method: \"POST\",\n  headers: {\n    \"X-Api-Key\": \"YOUR_API_KEY\",\n    \"Content-Type\": \"application\u002Fjson\",\n  },\n  body: JSON.stringify({\n    title: \"Collect and check documents\",\n    sortIndex: 100,\n    isImportant: true,\n  }),\n});\nconst { data } = await res.json();\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch(\"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Ftasks\u002F3943\u002Fchecklist\", {\n  method: \"POST\",\n  headers: {\n    \"X-Api-Key\": \"YOUR_APP_KEY\",\n    \"Authorization\": \"Bearer USER_SESSION_TOKEN\",\n    \"Content-Type\": \"application\u002Fjson\",\n  },\n  body: JSON.stringify({\n    title: \"Collect and check documents\",\n    sortIndex: 100,\n    isImportant: true,\n  }),\n});\nconst { data } = await res.json();\n```\n\nTo create a **new checklist** (a top-level container), pass `parentId: 0` — in this case `title` becomes the name of the checklist:\n\n```bash\ncurl -X POST \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Ftasks\u002F3943\u002Fchecklist\" \\\n  -H \"X-Api-Key: YOUR_API_KEY\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{ \"title\": \"Documents\", \"parentId\": 0 }'\n```\n\n## Response fields\n\n| Field | Type | Description |\n|------|-----|---------|\n| `success` | boolean | Always `true` on success |\n| `data.id` | number | ID of the new item |\n\n## Response example\n\n```json\n{ \"success\": true, \"data\": { \"id\": 221 } }\n```\n\n## Error response example\n\n`400` — the required `title` was not provided:\n\n```json\n{\n  \"success\": false,\n  \"error\": { \"code\": \"INVALID_PARAMS\", \"message\": \"`title` is required\" }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|---------|\n| 400 | `INVALID_PARAMS` | `title` is missing, `taskId` is not a positive integer, an unknown `members` shape, or a negative `parentId` |\n| 404 | `TASK_NOT_FOUND` | The `taskId` task does not exist or is not accessible to the key — Vibecode checks the parent task with a separate call before adding an item |\n| 403 | `SCOPE_DENIED` | The API key lacks the `task` scope |\n| 403 | `WRITE_BLOCKED_READONLY_KEY` | The key is in read-only mode. Open the path from `error.details.switchUrl`: a personal key points to `\u002Fkeys`, an application key with a card to `\u002Fapplications`, a standalone OAuth key to `\u002Fapps`, and a management key to `\u002Fmanagement-keys`. Switch it to read and write there |\n| 401 | `TOKEN_MISSING` | The API key has no configured tokens |\n\nFull list of common API errors — [Errors](\u002Fdocs\u002Ferrors).\n\n## Known specifics\n\n- **`parentId: 0` creates a new checklist container**, not a regular item — `title` becomes the container's name in this case.\n- **An item without an explicit `parentId` can land inside an existing checklist.** If the task already has a container (`parentId: 0`), Bitrix24 assigns new items to it instead of leaving them at the top level — create a container explicitly via `parentId: 0` if you need an independent one.\n- **`members` on write is an object keyed by `userId`**, not an array. The response shape (in `GET`) differs — see [\"List items\"](.\u002Flist.md).\n\n## See also\n\n- [List items](.\u002Flist.md)\n- [Update an item](.\u002Fupdate.md)\n- [Employees](\u002Fdocs\u002Fentities\u002Fusers)\n- [Tasks](\u002Fdocs\u002Fentities\u002Ftasks)\n","2026-11-12",{},1794739431495]