[{"data":1,"prerenderedAt":7},["ShallowReactive",2],{"docs-entities\u002Ftasks\u002Fchecklist\u002Fget":3,"docs-tabs-entities\u002Ftasks\u002Fchecklist\u002Fget":6},{"content":4,"lastmod":5},"## Get a checklist item\n\n`GET \u002Fv1\u002Ftasks\u002F:taskId\u002Fchecklist\u002F:itemId`\n\nReturns a single checklist item by ID.\n\n## Parameters\n\n| Parameter | Type | Required | Description |\n|----------|-----|:-----:|---------|\n| `taskId` (path) | integer | yes | Task ID |\n| `itemId` (path) | integer | yes | Checklist item ID. List of items — [`GET \u002Fv1\u002Ftasks\u002F:taskId\u002Fchecklist`](.\u002Flist.md) |\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Ftasks\u002F3943\u002Fchecklist\u002F213\" \\\n  -H \"X-Api-Key: YOUR_API_KEY\"\n```\n\n### curl — OAuth application\n\n```bash\ncurl \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Ftasks\u002F3943\u002Fchecklist\u002F213\" \\\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(\n  \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Ftasks\u002F3943\u002Fchecklist\u002F213\",\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(\n  \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Ftasks\u002F3943\u002Fchecklist\u002F213\",\n  {\n    headers: {\n      \"X-Api-Key\": \"YOUR_APP_KEY\",\n      \"Authorization\": \"Bearer USER_SESSION_TOKEN\",\n    },\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` | object | The checklist item. Its fields are in the `data.*` rows below |\n| `data.id` | string | Item ID |\n| `data.taskId` | string | Parent task ID |\n| `data.parentId` | integer \u002F string | Parent item ID. `0` — a top-level item |\n| `data.title` | string | Item text |\n| `data.sortIndex` | string | Sort index |\n| `data.isComplete` | string | Completion status — `\"Y\"` \u002F `\"N\"` |\n| `data.isImportant` | string | Importance flag — `\"Y\"` \u002F `\"N\"` |\n| `data.createdBy` | string | Item author |\n| `data.toggledBy` | string \\| null | Who last changed the completion status |\n| `data.toggledDate` | string | When the status was last changed. An empty string if never changed |\n| `data.members` | array | Item members — objects `{ id, type, name, personalPhoto, personalGender, image, isCollaber }` |\n| `data.attachments` | array \\| object | Item attachments. An empty array if there are none. Otherwise, an object keyed by attachment ID; each value is an object with the fields `attachmentId`, `name`, `size`, `fileId` (the Drive file ID), `downloadUrl`, and `viewUrl` |\n\n## Response example\n\n```json\n{\n  \"success\": true,\n  \"data\": {\n    \"id\": \"213\",\n    \"taskId\": \"3943\",\n    \"parentId\": \"211\",\n    \"createdBy\": \"1317\",\n    \"title\": \"Collect and check documents\",\n    \"sortIndex\": \"100\",\n    \"isComplete\": \"N\",\n    \"isImportant\": \"Y\",\n    \"toggledBy\": null,\n    \"toggledDate\": \"\",\n    \"members\": [\n      {\n        \"id\": \"1317\",\n        \"type\": \"A\",\n        \"name\": \"Jane Doe\",\n        \"personalPhoto\": \"35959\",\n        \"personalGender\": \"\",\n        \"image\": \"https:\u002F\u002Fexample.bitrix24.com\u002F...\",\n        \"isCollaber\": false\n      }\n    ],\n    \"attachments\": []\n  }\n}\n```\n\n## Error response example\n\n`404` — the item does not exist or is not accessible:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"NOT_FOUND\",\n    \"message\": \"Checklist item not found\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|---------|\n| 400 | `INVALID_PARAMS` | `taskId` or `itemId` is not a positive integer |\n| 404 | `NOT_FOUND` | The item with the given `itemId` was deleted, never existed, or is not accessible to the key |\n| 404 | `TASK_NOT_FOUND` | Bitrix24 reported that the parent task is missing or not accessible to the key |\n| 403 | `SCOPE_DENIED` | The API key lacks the `task` scope |\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 missing item returns `404 NOT_FOUND`.** Requests for a nonexistent or deleted `itemId` previously returned `422 BITRIX_ERROR` with the message from an internal Bitrix24 exception (`ITEM_NOT_FOUND_OR_NOT_ACCESSIBLE`). The response now matches those of the other task routes.\n\n## See also\n\n- [List items](.\u002Flist.md)\n- [Update an item](.\u002Fupdate.md)\n- [Tasks](\u002Fdocs\u002Fentities\u002Ftasks)\n","2026-10-20",{},1794739431813]