[{"data":1,"prerenderedAt":13},["ShallowReactive",2],{"docs-notifications\u002Fgroups":3,"docs-tabs-notifications\u002Fgroups":6},{"content":4,"lastmod":5},"# Notification groups\n\nA notification group selects a user's notifications by the module and the event they came from. A module and event pair is a group condition. The operations list groups, create a group with its first condition, rename and delete it, add and remove conditions.\n\n**Scope:** `im` | **Base URL:** `https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1` | **Authorization:** `X-Api-Key`\n\n## Operations\n\n- [List notification groups](.\u002Fgroups\u002Flist.md) — `GET \u002Fv1\u002Fnotifications\u002Fgroups`\n- [Create a notification group](.\u002Fgroups\u002Fcreate.md) — `POST \u002Fv1\u002Fnotifications\u002Fgroups`\n- [Rename a notification group](.\u002Fgroups\u002Fupdate.md) — `PATCH \u002Fv1\u002Fnotifications\u002Fgroups\u002F:groupId`\n- [Delete a notification group](.\u002Fgroups\u002Fdelete.md) — `DELETE \u002Fv1\u002Fnotifications\u002Fgroups\u002F:groupId`\n- [Add a condition to a notification group](.\u002Fgroups\u002Fconditions-create.md) — `POST \u002Fv1\u002Fnotifications\u002Fgroups\u002F:groupId\u002Fconditions`\n- [Remove a condition from a notification group](.\u002Fgroups\u002Fconditions-delete.md) — `DELETE \u002Fv1\u002Fnotifications\u002Fgroups\u002F:groupId\u002Fconditions`\n\n## Whose groups\n\nGroups belong to the user on whose behalf the call is made. With a personal key, this is the key owner; with an OAuth application key, it is the session user from the `Authorization: Bearer` header. Only a group the user created can be renamed, deleted or have its conditions changed — in the group list it has `isEditable: true`.\n\n## See also\n\n- [Notifications](\u002Fdocs\u002Fnotifications)\n- [Notification settings](\u002Fdocs\u002Fnotifications\u002Fsettings)\n- [Notification feed](\u002Fdocs\u002Fnotifications\u002Flist)\n","2026-10-09",{"groups\u002Flist.md":7,"groups\u002Fcreate.md":8,"groups\u002Fupdate.md":9,"groups\u002Fdelete.md":10,"groups\u002Fconditions-create.md":11,"groups\u002Fconditions-delete.md":12},"## List notification groups\n\n`GET \u002Fv1\u002Fnotifications\u002Fgroups`\n\nReturns the user's notification groups: system ones and the ones the user created. Call it before changing a group to learn its identifier and current conditions.\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fnotifications\u002Fgroups\" \\\n  -H \"X-Api-Key: YOUR_API_KEY\"\n```\n\n### curl — OAuth application\n\n```bash\ncurl \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fnotifications\u002Fgroups\" \\\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\u002Fnotifications\u002Fgroups', {\n  headers: { 'X-Api-Key': 'YOUR_API_KEY' },\n})\n\nconst { data } = await res.json()\nconst ownGroups = data.items.filter((group) => group.isEditable)\nconsole.log('Own groups:', ownGroups.length)\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fnotifications\u002Fgroups', {\n  headers: {\n    'X-Api-Key': 'YOUR_APP_KEY',\n    'Authorization': 'Bearer USER_SESSION_TOKEN',\n  },\n})\n\nconst { data } = await res.json()\nconst ownGroups = data.items.filter((group) => group.isEditable)\nconsole.log('Own groups:', ownGroups.length)\n```\n\n## Response fields\n\n| Field | Type | Description |\n|------|-----|---------|\n| `success` | boolean | Always `true` on success |\n| `data.items` | array | Notification groups: system ones first, followed by the ones the user created |\n| `data.items[].tag` | string | Group identifier. For a system group it is a tag: `confirm`, `mention` or `admin`. For a user group it is a numeric identifier as a string, for example `\"12\"`. It is passed as a number in the `:groupId` path parameter of [Rename a notification group](\u002Fdocs\u002Fnotifications\u002Fgroups\u002Fupdate), [Delete a notification group](\u002Fdocs\u002Fnotifications\u002Fgroups\u002Fdelete), [Add a condition to a notification group](\u002Fdocs\u002Fnotifications\u002Fgroups\u002Fconditions-create) and [Remove a condition from a notification group](\u002Fdocs\u002Fnotifications\u002Fgroups\u002Fconditions-delete) |\n| `data.items[].title` | string | Group name |\n| `data.items[].isEditable` | boolean | `false` for a system group — it cannot be renamed or deleted, and its conditions cannot be changed. `true` for a user group |\n| `data.items[].conditions` | object | Conditions by which the group selects notifications |\n| `data.items[].conditions.notifyType` | number | Present only on the `confirm` group. The value `1` means the group selects confirmation requests — notifications with reply buttons |\n| `data.items[].conditions.moduleConditions` | object | Conditions by module. The key is the module identifier as is, for example `tasks` or `vendor.my_module`. The `all` key is a condition without a module |\n| `data.items[].conditions.moduleConditions.\u003Cmodule>.isWhole` | boolean | `true` — the group selects all events of the module, and the `events` list does not restrict the selection. `false` — only the events listed in `events` |\n| `data.items[].conditions.moduleConditions.\u003Cmodule>.events` | array | Identifiers of the module events the group selects |\n\n## Response example\n\nHTTP 200:\n\n```json\n{\n  \"success\": true,\n  \"data\": {\n    \"items\": [\n      {\n        \"tag\": \"confirm\",\n        \"title\": \"Require action\",\n        \"conditions\": { \"notifyType\": 1 },\n        \"isEditable\": false\n      },\n      {\n        \"tag\": \"mention\",\n        \"title\": \"I was mentioned\",\n        \"conditions\": {\n          \"moduleConditions\": {\n            \"all\": { \"isWhole\": false, \"events\": [\"mention\", \"mention_comment\"] }\n          }\n        },\n        \"isEditable\": false\n      },\n      {\n        \"tag\": \"12\",\n        \"title\": \"Tasks and calendar\",\n        \"conditions\": {\n          \"moduleConditions\": {\n            \"tasks\": { \"isWhole\": false, \"events\": [\"comment\"] },\n            \"calendar\": { \"isWhole\": false, \"events\": [\"invite\"] }\n          }\n        },\n        \"isEditable\": true\n      }\n    ]\n  }\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 `limit` is not accepted by GET \u002Fv1\u002Fnotifications\u002Fgroups. It takes no query parameters.\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|----------|\n| 400 | `INVALID_PARAMS` | A query parameter was passed — the operation does not accept query parameters. The parameter name is in `message` |\n| 422 | `BITRIX_ERROR` | Bitrix24 rejected the request; the portal code is in the `error.b24Code` field |\n| 403 | `SCOPE_DENIED` | The key lacks the `im` scope |\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- Groups belong to the user on whose behalf the call is made. With a personal key, this is the key owner; with an OAuth application key, it is the session user from the `Authorization: Bearer` header. All group operations and [group conditions](\u002Fdocs\u002Fnotifications\u002Fgroups) work with the groups of the same user.\n\n## See also\n\n- [Create a notification group](\u002Fdocs\u002Fnotifications\u002Fgroups\u002Fcreate)\n- [Rename a notification group](\u002Fdocs\u002Fnotifications\u002Fgroups\u002Fupdate)\n- [Delete a notification group](\u002Fdocs\u002Fnotifications\u002Fgroups\u002Fdelete)\n- [Add a condition to a notification group](\u002Fdocs\u002Fnotifications\u002Fgroups\u002Fconditions-create)\n- [Notification groups](\u002Fdocs\u002Fnotifications\u002Fgroups)\n","## Create a notification group\n\n`POST \u002Fv1\u002Fnotifications\u002Fgroups`\n\nCreates a notification group together with its first condition — a module and event pair. Further conditions are added to an existing group with the [Add a condition to a notification group](\u002Fdocs\u002Fnotifications\u002Fgroups\u002Fconditions-create) operation.\n\n## Request fields (body)\n\n| Field | Type | Required | Description |\n|------|-----|:-----:|---------|\n| `title` | string | yes | Group name, 1 to 255 characters |\n| `module` | string | yes | Module identifier of the first condition, 1 to 255 characters. Modules are listed in the `data[].id` field of [`GET \u002Fv1\u002Fnotifications\u002Fsettings`](\u002Fdocs\u002Fnotifications\u002Fsettings\u002Flist); the module of a specific notification is in the `notifyModule` field of the [notification feed](\u002Fdocs\u002Fnotifications\u002Flist) |\n| `event` | string | yes | Identifier of an event of this module, 1 to 255 characters. The module's events are listed in the `data[].notices[].id` field of [`GET \u002Fv1\u002Fnotifications\u002Fsettings`](\u002Fdocs\u002Fnotifications\u002Fsettings\u002Flist); the event of a specific notification is in the `notifyEvent` field of the [notification feed](\u002Fdocs\u002Fnotifications\u002Flist) |\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl -X POST \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fnotifications\u002Fgroups\" \\\n  -H \"X-Api-Key: YOUR_API_KEY\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{ \"title\": \"Tasks and calendar\", \"module\": \"tasks\", \"event\": \"comment\" }'\n```\n\n### curl — OAuth application\n\n```bash\ncurl -X POST \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fnotifications\u002Fgroups\" \\\n  -H \"X-Api-Key: YOUR_APP_KEY\" \\\n  -H \"Authorization: Bearer USER_SESSION_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{ \"title\": \"Tasks and calendar\", \"module\": \"tasks\", \"event\": \"comment\" }'\n```\n\n### JavaScript — personal key\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fnotifications\u002Fgroups', {\n  method: 'POST',\n  headers: {\n    'X-Api-Key': 'YOUR_API_KEY',\n    'Content-Type': 'application\u002Fjson',\n  },\n  body: JSON.stringify({ title: 'Tasks and calendar', module: 'tasks', event: 'comment' }),\n})\n\nconst { data } = await res.json()\nconsole.log('Group ID:', data.id)\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fnotifications\u002Fgroups', {\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({ title: 'Tasks and calendar', module: 'tasks', event: 'comment' }),\n})\n\nconst { data } = await res.json()\nconsole.log('Group ID:', data.id)\n```\n\n## Response fields\n\n| Field | Type | Description |\n|------|-----|---------|\n| `success` | boolean | Always `true` on success |\n| `data.id` | number | Identifier of the new group. In the group list it arrives as a string in the `tag` field |\n\n## Response example\n\nHTTP 200:\n\n```json\n{\n  \"success\": true,\n  \"data\": {\n    \"id\": 12\n  }\n}\n```\n\n## Error response example\n\n400 — `title` was not passed:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"INVALID_PARAMS\",\n    \"message\": \"Body field `title` must be a non-empty string of up to 255 characters.\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|----------|\n| 400 | `INVALID_PARAMS` | `title`, `module` or `event` was not passed, is not a string, is an empty string or is longer than 255 characters. The field name is in `message` |\n| 400 | `INVALID_PARAMS` | A body field not listed in the table above or a query parameter was passed, or the body is not a JSON object |\n| 422 | `BITRIX_ERROR` | Bitrix24 rejected the creation; the portal 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## See also\n\n- [List notification groups](\u002Fdocs\u002Fnotifications\u002Fgroups\u002Flist)\n- [Add a condition to a notification group](\u002Fdocs\u002Fnotifications\u002Fgroups\u002Fconditions-create)\n- [Get notification settings](\u002Fdocs\u002Fnotifications\u002Fsettings\u002Flist)\n- [Notification feed](\u002Fdocs\u002Fnotifications\u002Flist)\n","## Rename a notification group\n\n`PATCH \u002Fv1\u002Fnotifications\u002Fgroups\u002F:groupId`\n\nChanges the name of a group the user created. The group's conditions do not change — they are edited with the [Add a condition to a notification group](\u002Fdocs\u002Fnotifications\u002Fgroups\u002Fconditions-create) and [Remove a condition from a notification group](\u002Fdocs\u002Fnotifications\u002Fgroups\u002Fconditions-delete) operations.\n\n## Parameters\n\n| Parameter | Type | Required | Description |\n|----------|-----|:-----:|---------|\n| `groupId` (path) | number | yes | Group identifier — the `tag` value of a group with `isEditable: true` from the [group list](\u002Fdocs\u002Fnotifications\u002Fgroups\u002Flist), passed as a number. The system groups `confirm`, `mention` and `admin` have no numeric identifier |\n\n## Request fields (body)\n\n| Field | Type | Required | Description |\n|------|-----|:-----:|---------|\n| `title` | string | yes | New group name, 1 to 255 characters |\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl -X PATCH \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fnotifications\u002Fgroups\u002F12\" \\\n  -H \"X-Api-Key: YOUR_API_KEY\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{ \"title\": \"Work notifications\" }'\n```\n\n### curl — OAuth application\n\n```bash\ncurl -X PATCH \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fnotifications\u002Fgroups\u002F12\" \\\n  -H \"X-Api-Key: YOUR_APP_KEY\" \\\n  -H \"Authorization: Bearer USER_SESSION_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{ \"title\": \"Work notifications\" }'\n```\n\n### JavaScript — personal key\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fnotifications\u002Fgroups\u002F12', {\n  method: 'PATCH',\n  headers: {\n    'X-Api-Key': 'YOUR_API_KEY',\n    'Content-Type': 'application\u002Fjson',\n  },\n  body: JSON.stringify({ title: 'Work notifications' }),\n})\n\nconst { success } = await res.json()\nconsole.log('Group renamed:', success)\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fnotifications\u002Fgroups\u002F12', {\n  method: 'PATCH',\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({ title: 'Work notifications' }),\n})\n\nconst { success } = await res.json()\nconsole.log('Group renamed:', success)\n```\n\n## Response fields\n\n| Field | Type | Description |\n|------|-----|---------|\n| `success` | boolean | Always `true` on success |\n| `data.result` | boolean | Always `true`. The success indicator is the HTTP status `200`, not this value |\n\n## Response example\n\nHTTP 200:\n\n```json\n{\n  \"success\": true,\n  \"data\": {\n    \"result\": true\n  }\n}\n```\n\n## Error response example\n\n404 — the group does not exist:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"ENTITY_NOT_FOUND\",\n    \"message\": \"Notification group was not found.\",\n    \"b24Code\": \"GROUP_NOT_FOUND\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|----------|\n| 400 | `INVALID_PARAMS` | `groupId` is not a positive integer, including a system group tag such as `mention` |\n| 400 | `INVALID_PARAMS` | `title` was not passed, is not a string, is an empty string or is longer than 255 characters |\n| 400 | `INVALID_PARAMS` | A body field not listed in the table above or a query parameter was passed, or the body is not a JSON object. The field name is in `message` |\n| 404 | `ENTITY_NOT_FOUND` | The group does not exist — it was deleted or belongs to another user. The portal code `GROUP_NOT_FOUND` is in the `error.b24Code` field. On a portal whose interface language is neither Russian nor English, the same refusal arrives as `422 BITRIX_ERROR` — rely on `error.b24Code` |\n| 422 | `BITRIX_ERROR` | Bitrix24 rejected the change. The portal 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## See also\n\n- [List notification groups](\u002Fdocs\u002Fnotifications\u002Fgroups\u002Flist)\n- [Delete a notification group](\u002Fdocs\u002Fnotifications\u002Fgroups\u002Fdelete)\n- [Add a condition to a notification group](\u002Fdocs\u002Fnotifications\u002Fgroups\u002Fconditions-create)\n","## Delete a notification group\n\n`DELETE \u002Fv1\u002Fnotifications\u002Fgroups\u002F:groupId`\n\nDeletes a group the user created, together with all its conditions; the notifications themselves stay in the feed. A deleted group cannot be restored via the API — create a new one if needed.\n\n## Parameters\n\n| Parameter | Type | Required | Description |\n|----------|-----|:-----:|---------|\n| `groupId` (path) | number | yes | Group identifier — the `tag` value of a group with `isEditable: true` from the [group list](\u002Fdocs\u002Fnotifications\u002Fgroups\u002Flist), passed as a number. The system groups `confirm`, `mention` and `admin` have no numeric identifier |\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl -X DELETE \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fnotifications\u002Fgroups\u002F12\" \\\n  -H \"X-Api-Key: YOUR_API_KEY\"\n```\n\n### curl — OAuth application\n\n```bash\ncurl -X DELETE \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fnotifications\u002Fgroups\u002F12\" \\\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\u002Fnotifications\u002Fgroups\u002F12', {\n  method: 'DELETE',\n  headers: { 'X-Api-Key': 'YOUR_API_KEY' },\n})\n\nconst { success } = await res.json()\nconsole.log('Group deleted:', success)\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fnotifications\u002Fgroups\u002F12', {\n  method: 'DELETE',\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('Group deleted:', success)\n```\n\n## Response fields\n\n| Field | Type | Description |\n|------|-----|---------|\n| `success` | boolean | Always `true` on success |\n| `data.result` | boolean | Always `true`. The success indicator is the HTTP code `200`, not the value |\n\n## Response example\n\nHTTP 200:\n\n```json\n{\n  \"success\": true,\n  \"data\": {\n    \"result\": true\n  }\n}\n```\n\n## Error response example\n\n404 — the group does not exist:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"ENTITY_NOT_FOUND\",\n    \"message\": \"Notification group was not found.\",\n    \"b24Code\": \"GROUP_NOT_FOUND\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|----------|\n| 400 | `INVALID_PARAMS` | `groupId` is not a positive integer, including a system group tag such as `mention` |\n| 400 | `INVALID_PARAMS` | A body field or a query parameter was passed — the operation does not accept them — or the body is not a JSON object. The field name is in `message` |\n| 404 | `ENTITY_NOT_FOUND` | The group does not exist — it was already deleted (including automatically, when its last [condition](\u002Fdocs\u002Fnotifications\u002Fgroups\u002Fconditions-delete) was removed) or belongs to another user. The portal code `GROUP_NOT_FOUND` is in the `error.b24Code` field. On a portal whose interface language is neither Russian nor English, the same refusal arrives as `422 BITRIX_ERROR` — rely on `error.b24Code` |\n| 422 | `BITRIX_ERROR` | Bitrix24 rejected the deletion; the portal 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## See also\n\n- [List notification groups](\u002Fdocs\u002Fnotifications\u002Fgroups\u002Flist)\n- [Create a notification group](\u002Fdocs\u002Fnotifications\u002Fgroups\u002Fcreate)\n- [Remove a condition from a notification group](\u002Fdocs\u002Fnotifications\u002Fgroups\u002Fconditions-delete)\n","## Add a condition to a notification group\n\n`POST \u002Fv1\u002Fnotifications\u002Fgroups\u002F:groupId\u002Fconditions`\n\nAdds one more module and event pair to a group the user created. From then on, the group also selects notifications of this event.\n\n## Parameters\n\n| Parameter | Type | Required | Description |\n|----------|-----|:-----:|---------|\n| `groupId` (path) | number | yes | Group identifier — the `tag` value of a group with `isEditable: true` from the [group list](\u002Fdocs\u002Fnotifications\u002Fgroups\u002Flist), passed as a number. The system groups `confirm`, `mention` and `admin` have no numeric identifier |\n\n## Request fields (body)\n\n| Field | Type | Required | Description |\n|------|-----|:-----:|---------|\n| `module` | string | yes | Module identifier, 1 to 255 characters. The list of modules is the `data[].id` field in the [notification settings](\u002Fdocs\u002Fnotifications\u002Fsettings\u002Flist); the module of a specific notification is the `notifyModule` field in the [notification feed](\u002Fdocs\u002Fnotifications\u002Flist) |\n| `event` | string | yes | Identifier of an event of this module, 1 to 255 characters. The module's events are the `data[].notices[].id` field in the [notification settings](\u002Fdocs\u002Fnotifications\u002Fsettings\u002Flist); the event of a specific notification is the `notifyEvent` field in the [notification feed](\u002Fdocs\u002Fnotifications\u002Flist) |\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl -X POST \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fnotifications\u002Fgroups\u002F12\u002Fconditions\" \\\n  -H \"X-Api-Key: YOUR_API_KEY\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{ \"module\": \"calendar\", \"event\": \"invite\" }'\n```\n\n### curl — OAuth application\n\n```bash\ncurl -X POST \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fnotifications\u002Fgroups\u002F12\u002Fconditions\" \\\n  -H \"X-Api-Key: YOUR_APP_KEY\" \\\n  -H \"Authorization: Bearer USER_SESSION_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{ \"module\": \"calendar\", \"event\": \"invite\" }'\n```\n\n### JavaScript — personal key\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fnotifications\u002Fgroups\u002F12\u002Fconditions', {\n  method: 'POST',\n  headers: {\n    'X-Api-Key': 'YOUR_API_KEY',\n    'Content-Type': 'application\u002Fjson',\n  },\n  body: JSON.stringify({ module: 'calendar', event: 'invite' }),\n})\n\nconst { data } = await res.json()\nconsole.log('Condition ID:', data.id)\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fnotifications\u002Fgroups\u002F12\u002Fconditions', {\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({ module: 'calendar', event: 'invite' }),\n})\n\nconst { data } = await res.json()\nconsole.log('Condition ID:', data.id)\n```\n\n## Response fields\n\n| Field | Type | Description |\n|------|-----|---------|\n| `success` | boolean | Always `true` on success |\n| `data.id` | number | Condition identifier. You do not need it to [remove the condition](\u002Fdocs\u002Fnotifications\u002Fgroups\u002Fconditions-delete) — a condition is identified by its `module` and `event` pair |\n\n## Response example\n\nHTTP 200:\n\n```json\n{\n  \"success\": true,\n  \"data\": {\n    \"id\": 31\n  }\n}\n```\n\n## Error response example\n\n422 — the group already has this condition:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"BITRIX_ERROR\",\n    \"message\": \"Mysql query error: (1062) Duplicate entry '12-calendar-invite' for key 'b_im_notify_group_condition.UX_IM_NOTIFY_GROUP_CONDITION_GROUP_ID_MODULE_EVENT'\",\n    \"b24Code\": \"400\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|----------|\n| 400 | `INVALID_PARAMS` | `groupId` is not a positive integer, including a system group tag such as `mention` |\n| 400 | `INVALID_PARAMS` | `module` or `event` was not passed, is not a string, is an empty string or is longer than 255 characters. The field name is in `message` |\n| 400 | `INVALID_PARAMS` | A body field not listed in the table above or a query parameter was passed, or the body is not a JSON object |\n| 404 | `ENTITY_NOT_FOUND` | The group does not exist — it was deleted or belongs to another user. The portal code `GROUP_NOT_FOUND` is in the `error.b24Code` field. On a portal whose interface language is neither Russian nor English, the same refusal arrives as `422 BITRIX_ERROR` — rely on `error.b24Code` |\n| 422 | `BITRIX_ERROR` | The group already has this condition. `error.b24Code` holds `400`, and `message` holds the Bitrix24 database error text about a duplicate entry. A duplicate has no separate code — check the group's contents in the [group list](\u002Fdocs\u002Fnotifications\u002Fgroups\u002Flist) before adding |\n| 422 | `BITRIX_ERROR` | Bitrix24 rejected the addition for another reason; the portal 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## See also\n\n- [Notification groups](\u002Fdocs\u002Fnotifications\u002Fgroups)\n- [Remove a condition from a notification group](\u002Fdocs\u002Fnotifications\u002Fgroups\u002Fconditions-delete)\n- [Create a notification group](\u002Fdocs\u002Fnotifications\u002Fgroups\u002Fcreate)\n- [Get notification settings](\u002Fdocs\u002Fnotifications\u002Fsettings\u002Flist)\n","## Remove a condition from a notification group\n\n`DELETE \u002Fv1\u002Fnotifications\u002Fgroups\u002F:groupId\u002Fconditions`\n\nRemoves a single condition from a group the user created — the module and event pair named in the query parameters.\n\n## Parameters\n\n| Parameter | Type | Required | Description |\n|----------|-----|:-----:|---------|\n| `groupId` (path) | number | yes | Group identifier — the `tag` value of a group with `isEditable: true` from the [group list](\u002Fdocs\u002Fnotifications\u002Fgroups\u002Flist), passed as a number |\n| `module` (query) | string | yes | Condition module, 1 to 255 characters, passed once. The group's modules are the keys of `conditions.moduleConditions` in the [group list](\u002Fdocs\u002Fnotifications\u002Fgroups\u002Flist) |\n| `event` (query) | string | yes | Condition event, 1 to 255 characters, passed once. The module's events are the `events` array under its key in `conditions.moduleConditions` |\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl -X DELETE \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fnotifications\u002Fgroups\u002F12\u002Fconditions?module=calendar&event=invite\" \\\n  -H \"X-Api-Key: YOUR_API_KEY\"\n```\n\n### curl — OAuth application\n\n```bash\ncurl -X DELETE \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fnotifications\u002Fgroups\u002F12\u002Fconditions?module=calendar&event=invite\" \\\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 params = new URLSearchParams({ module: 'calendar', event: 'invite' })\nconst res = await fetch(`https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fnotifications\u002Fgroups\u002F12\u002Fconditions?${params}`, {\n  method: 'DELETE',\n  headers: { 'X-Api-Key': 'YOUR_API_KEY' },\n})\n\nconst { success } = await res.json()\nconsole.log('Condition removed:', success)\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst params = new URLSearchParams({ module: 'calendar', event: 'invite' })\nconst res = await fetch(`https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fnotifications\u002Fgroups\u002F12\u002Fconditions?${params}`, {\n  method: 'DELETE',\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('Condition removed:', success)\n```\n\n## Response fields\n\n| Field | Type | Description |\n|------|-----|---------|\n| `success` | boolean | Always `true` on success |\n| `data.result` | boolean | Always `true`. The success indicator is the HTTP code `200`, not the value |\n\n## Response example\n\nHTTP 200:\n\n```json\n{\n  \"success\": true,\n  \"data\": {\n    \"result\": true\n  }\n}\n```\n\n## Error response example\n\n400 — `event` was not passed:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"INVALID_PARAMS\",\n    \"message\": \"Query parameter `event` must be a non-empty string of up to 255 characters.\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|----------|\n| 400 | `INVALID_PARAMS` | `groupId` is not a positive integer, including a system group tag such as `mention` |\n| 400 | `INVALID_PARAMS` | `module` or `event` was not passed, is empty, is longer than 255 characters or was passed twice. The parameter name is in `message` |\n| 400 | `INVALID_PARAMS` | Another query parameter or a body field was passed, or the body is not a JSON object. The name is in `message` |\n| 404 | `ENTITY_NOT_FOUND` | The group does not exist — it was deleted or belongs to another user. The portal code `GROUP_NOT_FOUND` is in the `error.b24Code` field. On a portal whose interface language is neither Russian nor English, the same refusal arrives as `422 BITRIX_ERROR` — rely on `error.b24Code` |\n| 422 | `BITRIX_ERROR` | Bitrix24 rejected the removal; the portal 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- Removing the last condition also deletes the group itself: it disappears from the [group list](\u002Fdocs\u002Fnotifications\u002Fgroups\u002Flist). To replace the only condition of a group, [add the new one](\u002Fdocs\u002Fnotifications\u002Fgroups\u002Fconditions-create) first, then remove the old one.\n- A request with a module and event pair the group does not have also returns `200` with `data.result: true`. Such a response does not confirm that the condition was in the group — check against the group list.\n\n## See also\n\n- [Notification groups](\u002Fdocs\u002Fnotifications\u002Fgroups)\n- [Add a condition to a notification group](\u002Fdocs\u002Fnotifications\u002Fgroups\u002Fconditions-create)\n- [Delete a notification group](\u002Fdocs\u002Fnotifications\u002Fgroups\u002Fdelete)\n- [List notification groups](\u002Fdocs\u002Fnotifications\u002Fgroups\u002Flist)\n",1794739591545]