[{"data":1,"prerenderedAt":7},["ShallowReactive",2],{"docs-notifications\u002Fread-all":3,"docs-tabs-notifications\u002Fread-all":6},{"content":4,"lastmod":5},"\n## Mark all as read\n\n`POST \u002Fv1\u002Fnotifications\u002Fread-all`\n\nMarks all of the key owner's notifications as read in a single call, without listing their identifiers.\n\n## Request fields (body)\n\n| Field | Type | Required | Description |\n|------|-----|:-----:|---------|\n| `excludeIds` | number[] | no | Notifications to leave unread — 0 to 100 positive integer identifiers. An identifier is the `id` field of a notification in the [feed](.\u002Flist.md) or `notificationId` from the [`POST \u002Fv1\u002Fnotifications`](.\u002Fsend.md) response. An empty list is equivalent to omitting the field |\n\nThe body is optional; if you omit it, omit the `Content-Type: application\u002Fjson` header as well. Any other body field and any query string parameter are rejected with `400 INVALID_PARAMS` before the Bitrix24 call.\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl -X POST \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fnotifications\u002Fread-all\" \\\n  -H \"X-Api-Key: YOUR_API_KEY\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{ \"excludeIds\": [38964] }'\n```\n\n### curl — OAuth application\n\n```bash\ncurl -X POST \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fnotifications\u002Fread-all\" \\\n  -H \"X-Api-Key: YOUR_APP_KEY\" \\\n  -H \"Authorization: Bearer USER_SESSION_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{ \"excludeIds\": [38964] }'\n```\n\n### JavaScript — personal key\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fnotifications\u002Fread-all', {\n  method: 'POST',\n  headers: {\n    'X-Api-Key': 'YOUR_API_KEY',\n    'Content-Type': 'application\u002Fjson',\n  },\n  body: JSON.stringify({ excludeIds: [38964] }),\n})\n\nconst { data } = await res.json()\nconsole.log('Unread remaining:', data.counter)\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fnotifications\u002Fread-all', {\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({ excludeIds: [38964] }),\n})\n\nconst { data } = await res.json()\n```\n\n## Response fields\n\n| Field | Type | Description |\n|------|-----|----------|\n| `success` | boolean | `true` on success |\n| `data.counter` | number | Unread notification counter after the call |\n| `data.excludeIds` | number[] | Notifications left unread: the ones passed in `excludeIds` and confirmations — notifications with reply buttons |\n\n## Response example\n\nHTTP 200:\n\n```json\n{\n  \"success\": true,\n  \"data\": {\n    \"counter\": 1,\n    \"excludeIds\": [38964]\n  }\n}\n```\n\n## Error response example\n\n400 — the `ids` field instead of `excludeIds`:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"INVALID_PARAMS\",\n    \"message\": \"Body field `ids` is not accepted by POST \u002Fv1\u002Fnotifications\u002Fread-all. Accepted: excludeIds.\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|----------|\n| 400 | `INVALID_PARAMS` | `excludeIds` is not an array of 0–100 positive integer identifiers, another body field or a query string parameter was passed, or the body is not a JSON object. The field is named in the message. Checked before the Bitrix24 call |\n| 400 | `FST_ERR_CTP_EMPTY_JSON_BODY` | The `Content-Type: application\u002Fjson` header was sent with an empty body. Send `{}` or remove the header |\n| 422 | `BITRIX_ERROR` | Bitrix24 rejected the call. The portal error code is in the `error.b24Code` field |\n| 403 | `SCOPE_DENIED` | The key lacks the `im` scope |\n| 403 | `WRITE_BLOCKED_READONLY_KEY` | The key is in read-only mode |\n| 401 | `TOKEN_MISSING` | The key has no configured tokens |\n\nFull list of common API errors — [Errors](\u002Fdocs\u002Ferrors).\n\n## Known specifics\n\n- With an OAuth application key and the `Authorization: Bearer` header, the operation marks the session user's notifications.\n- To mark only selected notifications as read, use the v2 mode of the [Mark as read](.\u002Fread.md) operation with the `ids` field.\n\n## See also\n\n- [Mark as read](.\u002Fread.md)\n- [Notification feed](.\u002Flist.md)\n- [Delete all notifications](.\u002Fdelete-all.md)\n- [Errors](\u002Fdocs\u002Ferrors)\n","2026-10-15",{},1794739592738]