[{"data":1,"prerenderedAt":7},["ShallowReactive",2],{"docs-entities\u002Ftasks\u002Fchecklist\u002Fcomplete":3,"docs-tabs-entities\u002Ftasks\u002Fchecklist\u002Fcomplete":6},{"content":4,"lastmod":5},"## Mark an item complete\n\n`POST \u002Fv1\u002Ftasks\u002F:taskId\u002Fchecklist\u002F:itemId\u002Fcomplete`\n\nMarks a checklist item as complete. Equivalent to [`PATCH`](.\u002Fupdate.md) with the body `{ \"isComplete\": true }`, but doesn't require passing the other fields.\n\n## Parameters\n\n| Parameter | Type | Required | Description |\n|----------|-----|:-----:|---------|\n| `taskId` (path) | integer | yes | Task ID. List: [`GET \u002Fv1\u002Ftasks`](\u002Fdocs\u002Fentities\u002Ftasks\u002Flist) |\n| `itemId` (path) | integer | yes | Checklist item ID. List: [`GET \u002Fv1\u002Ftasks\u002F:taskId\u002Fchecklist`](\u002Fdocs\u002Fentities\u002Ftasks\u002Fchecklist\u002Flist) |\n\nNo request body is required.\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl -X POST \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Ftasks\u002F3943\u002Fchecklist\u002F213\u002Fcomplete\" \\\n  -H \"X-Api-Key: YOUR_API_KEY\"\n```\n\n### curl — OAuth application\n\n```bash\ncurl -X POST \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Ftasks\u002F3943\u002Fchecklist\u002F213\u002Fcomplete\" \\\n  -H \"X-Api-Key: YOUR_APP_KEY\" \\\n  -H \"Authorization: Bearer USER_SESSION_TOKEN\"\n```\n\n### JavaScript — personal key\n\n```javascript\nconst res = await fetch(\"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Ftasks\u002F3943\u002Fchecklist\u002F213\u002Fcomplete\", {\n  method: \"POST\",\n  headers: { \"X-Api-Key\": \"YOUR_API_KEY\" },\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\u002F213\u002Fcomplete\", {\n  method: \"POST\",\n  headers: {\n    \"X-Api-Key\": \"YOUR_APP_KEY\",\n    \"Authorization\": \"Bearer USER_SESSION_TOKEN\",\n  },\n});\nconst { data } = await res.json();\n```\n\n## Response fields\n\n| Field | Type | Description |\n|------|-----|---------|\n| `success` | boolean | Always `true` on success |\n| `data.id` | number | Item ID |\n| `data.isComplete` | string | Always `\"Y\"` after a successful call |\n\n## Response example\n\n```json\n{ \"success\": true, \"data\": { \"id\": 213, \"isComplete\": \"Y\" } }\n```\n\n## Error response example\n\n`400` — invalid `itemId`:\n\n```json\n{\n  \"success\": false,\n  \"error\": { \"code\": \"INVALID_PARAMS\", \"message\": \"taskId and itemId must be positive integers\" }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|---------|\n| 400 | `INVALID_PARAMS` | `taskId` or `itemId` is not a positive integer |\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- **A nonexistent `itemId` and a nonexistent `taskId` both return `200`.** The response echoes the given `itemId` with `isComplete: \"Y\"` even when no such item exists — and even when the task itself is missing. A success status confirms neither that the item exists nor that it was marked complete. To verify, call [\"Get an item\"](.\u002Fget.md), which returns `404` both for a missing item and for a missing task.\n- **A refusal for a missing item has not been measured here.** The route maps a Bitrix24 \"item not found\" refusal to `404 NOT_FOUND`, as the neighbouring checklist methods do, but on a live Bitrix24 account this method never produced that refusal — the probe answered `200`, and in the tests the refusal is reproduced only with a mock. That is why `404` is not listed in the errors above.\n\n## See also\n\n- [Reopen](.\u002Frenew.md)\n- [Update an item](.\u002Fupdate.md)\n- [List items](.\u002Flist.md)\n- [Tasks](\u002Fdocs\u002Fentities\u002Ftasks)\n","2026-10-15",{},1794739431422]