[{"data":1,"prerenderedAt":7},["ShallowReactive",2],{"docs-chats\u002Fmembers\u002Fmentionable":3,"docs-tabs-chats\u002Fmembers\u002Fmentionable":6},{"content":4,"lastmod":5},"## Users to mention\n\n`GET \u002Fv1\u002Fchats\u002F:dialogId\u002Fusers\u002Fmentionable`\n\nReturns the chat members the current user can mention with `@`. The list contains active members, excluding the current user, members whose membership is hidden, and hidden bots.\n\n## Parameters\n\n| Parameter | Type | Required | Default | Description |\n|----------|-----|:-----:|-----------|---------|\n| `dialogId` (path) | string | yes | — | Dialog ID: `chatXXX` for a group chat, a user ID for a direct dialog, or the `me` alias. `chatXXX` is the `id` field of a [recent dialogs](\u002Fdocs\u002Fchats\u002Fdiscovery\u002Frecent) row, a user ID comes from the [user list](\u002Fdocs\u002Fentities\u002Fusers\u002Flist) |\n| `limit` (query) | number | no | 50 | How many members to return, from 1 to 200. A value outside the range is clamped, and the requested and applied values are returned in `meta.requestedLimit` and `meta.appliedLimit`. If omitted, the Bitrix24 account default of 50 applies |\n\nAny other parameter, or a repeated one, is rejected with `400 INVALID_PARAMS`.\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fchats\u002Fchat123\u002Fusers\u002Fmentionable?limit=20\" \\\n  -H \"X-Api-Key: YOUR_API_KEY\"\n```\n\n### curl — OAuth application\n\n```bash\ncurl \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fchats\u002Fchat123\u002Fusers\u002Fmentionable?limit=20\" \\\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\u002Fchat123\u002Fusers\u002Fmentionable?limit=20', {\n  headers: { 'X-Api-Key': 'YOUR_API_KEY' },\n})\n\nconst { data } = await res.json()\nconsole.log('Can be mentioned:', data.users.map((u) => u.name))\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fchats\u002Fchat123\u002Fusers\u002Fmentionable?limit=20', {\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 | Result object |\n| `data.users` | array | Members who can be mentioned |\n| `data.users[].id` | number | User ID |\n| `data.users[].name` | string | Full name |\n| `data.users[].firstName` | string | First name |\n| `data.users[].lastName` | string | Last name |\n| `data.users[].workPosition` | string | Job title |\n| `data.users[].avatar` | string | Avatar URL. An empty string when no avatar is set |\n| `data.users[].color` | string | Avatar color in hexadecimal format |\n| `data.users[].type` | string | User type: `user`, `extranet`, `bot` and others |\n| `data.users[].bot` | boolean | The user is a bot |\n| `data.users[].extranet` | boolean | An external user |\n| `data.users[].status` | string | Presence status, for example `online` |\n| `data.users[].lastActivityDate` | string | Time of the last activity (ISO 8601) |\n| `data.users[].absent` | boolean \\| string | `false` or the end date of the absence |\n| `data.users[].departments` | array | Department IDs |\n| `meta.requestedLimit` | number | The `limit` that was sent. Returned together with `appliedLimit`, and only when the value was outside the 1 to 200 range |\n| `meta.appliedLimit` | number | The applied `limit` value — only when it was clamped to a bound |\n\nThe user object also carries other messenger fields.\n\n## Response example\n\n```json\n{\n  \"success\": true,\n  \"data\": {\n    \"users\": [\n      {\n        \"id\": 7,\n        \"active\": true,\n        \"name\": \"John Brown\",\n        \"firstName\": \"John\",\n        \"lastName\": \"Brown\",\n        \"workPosition\": \"Designer\",\n        \"color\": \"#df532d\",\n        \"avatar\": \"\",\n        \"gender\": \"M\",\n        \"bot\": false,\n        \"extranet\": false,\n        \"status\": \"online\",\n        \"lastActivityDate\": \"2026-09-20T10:01:00+00:00\",\n        \"absent\": false,\n        \"departments\": [1],\n        \"type\": \"user\"\n      }\n    ]\n  }\n}\n```\n\n## Error response example\n\n400 — `limit` is not a number:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"INVALID_PARAMS\",\n    \"message\": \"`limit` must be an integer (1-200).\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|---------|\n| 400 | `INVALID_PARAMS` | A parameter other than `limit`, a repeated parameter or a non-numeric `limit`. Checked before any call to Bitrix24 |\n| 403 | `SCOPE_DENIED` | The API key does not have the `im` scope |\n| 403 | `WRITE_BLOCKED_READONLY_KEY` | Read-only key, and the chat is not confirmed: a value other than `chatN` was passed and the personal dialog was not found in the same employee's recent dialog list — up to 20 pages and 4000 rows — or the alias creates a dialog. Rejected before any call to Bitrix24 |\n| 403 | `WRITE_BLOCKED_READONLY_KEY` | Read-only key that is not an employee's personal key: an application key with a user session, a [management key](\u002Fdocs\u002Fmanagement-keys), or a key with an unconfirmed owner |\n| 401 | `TOKEN_MISSING` | The API key has no Bitrix24 tokens configured |\n| 404 | `ENTITY_NOT_FOUND` | Bitrix24 answered \"not found\". The Bitrix24 code is in `error.b24Code` |\n| 422 | `BITRIX_ERROR` | Bitrix24 returned an error. The Bitrix24 code is in `error.b24Code`. For a chat that does not exist, the code is `CHAT_NOT_FOUND` |\n| 502 | `ME_ALIAS_RESOLUTION_FAILED` | Failed to resolve the user when using the `me` alias |\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**The list may be shorter than `limit` and incomplete.** Hidden bots are filtered out after the members are fetched, so a page can be shorter than `limit`. There is no cursor: in a chat with more than 200 members, the list is not complete — read all members through the [list of members](\u002Fdocs\u002Fchats\u002Fmembers\u002Flist).\n\n**The call may make you a member.** If the chat allows auto-join, the call adds the current user as a member, just as opening the chat does. This read is allowed for a `READONLY` key under two conditions: it is an employee's personal key, and the chat is confirmed — `chatN` was passed or the personal dialog was found in the same employee's recent dialogs. The call itself does not mark messages as read. The `im` scope and the user's Bitrix24 permissions still apply.\n\n## See also\n\n- [Membership check](\u002Fdocs\u002Fchats\u002Fmembers\u002Fmembership)\n- [List members](\u002Fdocs\u002Fchats\u002Fmembers\u002Flist)\n- [Send a message](\u002Fdocs\u002Fchats\u002Fmessages\u002Fsend)\n- [Members](\u002Fdocs\u002Fchats\u002Fmembers)\n","2026-10-15",{},1794739544490]