[{"data":1,"prerenderedAt":7},["ShallowReactive",2],{"docs-chats\u002Fmanagement\u002Fread-section":3,"docs-tabs-chats\u002Fmanagement\u002Fread-section":6},{"content":4,"lastmod":5},"## Read a list section\n\n`POST \u002Fv1\u002Fchats\u002Frecent\u002Fread`\n\nMarks as read every chat in one section of the current user's dialog list — for example, all task chats — and resets their unread counters. Other sections do not change.\n\n## Parameters\n\nQuery parameters are not accepted: any of them is rejected with `400 INVALID_PARAMS`.\n\n## Request fields (body)\n\n| Field | Type | Required | Description |\n|------|-----|:-----:|---------|\n| `section` | string | yes | Section code: a Latin letter, then letters, digits or `_`, up to 64 characters. The sections a chat is counted in arrive in the `recentSections` field of the [unread counters](\u002Fdocs\u002Fchats\u002Fdiscovery\u002Fcounters) |\n| `parentId` | integer | no | ID of the chat whose descendants are read, such as a channel's comments. A JSON integer, `1` or more. Without the field, the whole section is read |\n\nOther body fields are rejected with `400 INVALID_PARAMS`.\n\nSection codes in Bitrix24: `default` — the common list, `chat` — group chats, `channel` and `openChannel` — channels, `collab` — collabs, `copilot` — chats with the AI assistant, `lines` — Open Channels, `tasksTask` — task chats, `calendar` — calendar event chats.\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl -X POST https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fchats\u002Frecent\u002Fread \\\n  -H \"X-Api-Key: YOUR_API_KEY\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"section\": \"tasksTask\"}'\n```\n\n### curl — OAuth application\n\n```bash\ncurl -X POST https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fchats\u002Frecent\u002Fread \\\n  -H \"X-Api-Key: YOUR_APP_KEY\" \\\n  -H \"Authorization: Bearer USER_SESSION_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"section\": \"tasksTask\"}'\n```\n\n### JavaScript — personal key\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fchats\u002Frecent\u002Fread', {\n  method: 'POST',\n  headers: {\n    'X-Api-Key': 'YOUR_API_KEY',\n    'Content-Type': 'application\u002Fjson',\n  },\n  body: JSON.stringify({ section: 'tasksTask' }),\n})\n\nconst { success, data } = await res.json()\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fchats\u002Frecent\u002Fread', {\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({ section: 'tasksTask' }),\n})\n\nconst { success, data } = await res.json()\n```\n\n## Response fields\n\n| Field | Type | Description |\n|------|-----|---------|\n| `success` | boolean | Always `true` on success |\n| `data.result` | boolean | `true` — the section is read. It also arrives when there was nothing to read |\n\n## Response example\n\n```json\n{\n  \"success\": true,\n  \"data\": {\n    \"result\": true\n  }\n}\n```\n\n## Error response example\n\n400 — no `section` field:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"INVALID_PARAMS\",\n    \"message\": \"`section` is required: the recent-list section to read, e.g. `default`.\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|---------|\n| 400 | `INVALID_PARAMS` | No `section`, no request body, `section` is not a section code, `parentId` is not a JSON integer or is less than `1`, an extra body field or a query parameter. Checked before the Bitrix24 call |\n| 422 | `BITRIX_ERROR` | Bitrix24 returned an error; the Bitrix24 code is in `error.b24Code` |\n| 403 | `SCOPE_DENIED` | The API key does not have the `im` scope |\n| 403 | `WRITE_BLOCKED_READONLY_KEY` | Read-only key: marking as read is a write, see [access rights](\u002Fdocs\u002Faccess-rights) |\n| 401 | `TOKEN_MISSING` | The API key has no Bitrix24 tokens configured |\n| 502 | `BITRIX_UNAVAILABLE` | Bitrix24 is unavailable or returned a server error |\n\nFull list of common API errors — [Errors](\u002Fdocs\u002Ferrors).\n\n## Known specifics\n\n**An unknown section succeeds with no effect.** A section code that does not exist in the Bitrix24 account returns `true`, and no counter changes. The response does not reveal a typo in `section`: check the code against the `recentSections` field of the [unread counters](\u002Fdocs\u002Fchats\u002Fdiscovery\u002Fcounters).\n\n**The call cannot be undone.** The \"unread\" marks and counters of the section's chats are reset at once. Reading is personal: it changes only the counters of the user on whose behalf the call is made.\n\n## See also\n\n- [Read all chats](\u002Fdocs\u002Fchats\u002Fmanagement\u002Fread-all)\n- [Mark as read](\u002Fdocs\u002Fchats\u002Fmessages\u002Fread)\n- [Unread counters](\u002Fdocs\u002Fchats\u002Fdiscovery\u002Fcounters)\n- [Chat management](\u002Fdocs\u002Fchats\u002Fmanagement)\n","2026-09-30",{},1794739542663]