[{"data":1,"prerenderedAt":7},["ShallowReactive",2],{"docs-chats\u002Fmessages\u002Fanchors":3,"docs-tabs-chats\u002Fmessages\u002Fanchors":6},{"content":4,"lastmod":5},"## Remove chat anchors\n\n`POST \u002Fv1\u002Fchats\u002F:dialogId\u002Fanchors\u002Fread`\n\nRemoves all your anchors in the chat. An anchor is a mark the Bitrix24 messenger places for you on an unread mention or on a reaction to your message: the client uses it to show the mention counter and to jump to the right message. To remove anchors only on selected messages, use [`POST \u002Fv1\u002Fchats\u002Fanchors\u002Fread`](\u002Fdocs\u002Fchats\u002Fmessages\u002Fanchors-messages).\n\n## Parameters\n\n| Parameter | Type | Required | Default | Description |\n|----------|-----|:-----:|-----------|---------|\n| `dialogId` (path) | string | yes | — | Dialog ID: a numeric user ID for direct messages, `chatXXX` for group chats — the `dialogId` field of a [recent dialogs](\u002Fdocs\u002Fchats\u002Fdiscovery\u002Frecent) row; a user ID comes from the [user list](\u002Fdocs\u002Fentities\u002Fusers\u002Flist). `me` — the current user's personal dialog |\n\nNo body is needed. Query parameters and body fields are rejected with `400 INVALID_PARAMS`.\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl -X POST \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fchats\u002Fchat42\u002Fanchors\u002Fread\" \\\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\u002Fchats\u002Fchat42\u002Fanchors\u002Fread\" \\\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\u002Fchats\u002Fchat42\u002Fanchors\u002Fread', {\n  method: 'POST',\n  headers: { 'X-Api-Key': 'YOUR_API_KEY' },\n})\n\nconst { success } = await res.json()\nconsole.log('Anchors removed:', success)\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fchats\u002Fchat42\u002Fanchors\u002Fread', {\n  method: 'POST',\n  headers: {\n    'X-Api-Key': 'YOUR_APP_KEY',\n    'Authorization': 'Bearer USER_SESSION_TOKEN',\n  },\n})\n\nconst { success } = await res.json()\nconsole.log('Anchors removed:', success)\n```\n\n## Response fields\n\n| Field | Type | Description |\n|------|-----|---------|\n| `success` | boolean | Always `true` on success |\n| `data` | boolean | `true`, even when there was nothing to remove |\n\n## Response example\n\n```json\n{\n  \"success\": true,\n  \"data\": true\n}\n```\n\n## Error response example\n\n400 — a query parameter was passed:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"INVALID_PARAMS\",\n    \"message\": \"Query parameter `foo` is not accepted by POST \u002Fv1\u002Fchats\u002F:dialogId\u002Fanchors\u002Fread. It takes no query parameters.\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|---------|\n| 400 | `INVALID_PARAMS` | A query parameter or a body field was passed. Checked before any call to Bitrix24 |\n| 404 | `ENTITY_NOT_FOUND` | Bitrix24 returned \"not found\"; the portal code is in `error.b24Code` |\n| 422 | `BITRIX_ERROR` | Bitrix24 returned an error; the portal code is in `error.b24Code` |\n| 403 | `SCOPE_DENIED` | The API key does not have the `im` scope |\n| 403 | `WRITE_BLOCKED_READONLY_KEY` | The key is read-only — see [access rights](\u002Fdocs\u002Faccess-rights) |\n| 401 | `TOKEN_MISSING` | The API key has no Bitrix24 tokens configured |\n| 502 | `ME_ALIAS_RESOLUTION_FAILED` | Could not resolve the current user for `dialogId` = `me` |\n\nThe full list of common API errors — [Errors](\u002Fdocs\u002Ferrors).\n\n## Known specifics\n\n**This is a write operation, even though the method is called `read`.** The call deletes marks, so a read-only key gets `403 WRITE_BLOCKED_READONLY_KEY` before any call to Bitrix24.\n\n**List of anchors.** To retrieve all your mention and reaction marks, [list unread anchors](\u002Fdocs\u002Fchats\u002Fmessages\u002Fanchors-list).\n\n**Messages do not become read.** Removing anchors does not move the read marker — to do that, [mark the dialog as read](\u002Fdocs\u002Fchats\u002Fmessages\u002Fread).\n\n## See also\n\n- [Remove message anchors](\u002Fdocs\u002Fchats\u002Fmessages\u002Fanchors-messages)\n- [Mark as read](\u002Fdocs\u002Fchats\u002Fmessages\u002Fread)\n- [Messages around a message](\u002Fdocs\u002Fchats\u002Fmessages\u002Fcontext)\n","2026-10-26",{},1794739545080]