[{"data":1,"prerenderedAt":7},["ShallowReactive",2],{"docs-chats\u002Fmembers\u002Factive":3,"docs-tabs-chats\u002Fmembers\u002Factive":6},{"content":4,"lastmod":5},"## Active members\n\n`GET \u002Fv1\u002Fchats\u002F:dialogId\u002Fusers\u002Factive`\n\nReturns the chat members as user cards, as a single page, in the chosen order. To list the most active members first, pass `sort=lastSendMessageId&order=desc`. The [member list in the v2 mode](\u002Fdocs\u002Fchats\u002Fmembers\u002Flist) pages through all members.\n\n## Parameters\n\n| Parameter | Type | Required | Default | Description |\n|----------|-----|:-----:|-----------|---------|\n| `dialogId` (path) | string | yes | — | Dialog identifier: `chatXXX` for a group chat, a user ID for the personal dialog with that user, or the alias `me` for the personal dialog with yourself |\n| `limit` (query) | number | no | 50 | How many members to return, from 1 to 200. An out-of-range value is clamped and echoed in `meta.requestedLimit` and `meta.appliedLimit` |\n| `sort` (query) | string | no | — | The sort key: `id` — the membership record, `lastSendMessageId` — the member's last message, `userId` — the user ID. Without `sort` the order is up to Bitrix24 |\n| `order` (query) | string | no | `desc` | The direction of `sort`: `desc` or `asc`, case-insensitive. Accepted only together with `sort` |\n\nOther parameters and repeated ones are rejected with `400 INVALID_PARAMS`.\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fchats\u002Fchat42\u002Fusers\u002Factive?sort=lastSendMessageId&order=desc&limit=10\" \\\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\u002Fchat42\u002Fusers\u002Factive?sort=lastSendMessageId&order=desc&limit=10\" \\\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\u002Fusers\u002Factive?sort=lastSendMessageId&order=desc&limit=10', {\n  headers: { 'X-Api-Key': 'YOUR_API_KEY' },\n})\n\nconst { data } = await res.json()\nconsole.log('Active:', data.map((u) => u.name))\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fchats\u002Fchat42\u002Fusers\u002Factive?sort=lastSendMessageId&order=desc&limit=10', {\n  headers: {\n    'X-Api-Key': 'YOUR_APP_KEY',\n    'Authorization': 'Bearer USER_SESSION_TOKEN',\n  },\n})\n\nconst { data } = await res.json()\nconsole.log('Active:', data.map((u) => u.name))\n```\n\n## Response fields\n\n| Field | Type | Description |\n|------|-----|---------|\n| `success` | boolean | Always `true` on success |\n| `data` | array | Member cards — the same fields as in the [member list](\u002Fdocs\u002Fchats\u002Fmembers\u002Flist) |\n| `data[].id` | number | User ID |\n| `data[].active` | boolean | Whether the account is active |\n| `data[].name` | string | Full name |\n| `data[].firstName` | string | First name |\n| `data[].lastName` | string | Last name |\n| `data[].workPosition` | string\\|null | Job title |\n| `data[].color` | string | Avatar color |\n| `data[].avatar` | string | Avatar URL. Empty string if no avatar is set |\n| `data[].gender` | string | Gender: `M` — male, `F` — female, empty string — not specified |\n| `data[].birthday` | string | Birth date. Empty string if not specified |\n| `data[].extranet` | boolean | External user, type `extranet` |\n| `data[].network` | boolean | Bitrix24.Network user |\n| `data[].connector` | boolean | Open Channels user of the Contact Center |\n| `data[].idle` | boolean | Idle |\n| `data[].absent` | boolean \\| string | `false` or the date the absence ends |\n| `data[].departments` | number[] | IDs of the user's departments. List: [`GET \u002Fv1\u002Fdepartments`](\u002Fdocs\u002Fentities\u002Fdepartments\u002Flist) |\n| `data[].status` | string | Status (`online`, `away`, `dnd`) |\n| `data[].lastActivityDate` | string | Last activity date (ISO 8601) |\n| `data[].bot` | boolean | Whether the user is a bot |\n| `data[].type` | string | User type (`user`, `bot`, `extranet`) |\n| `meta.requestedLimit` | number | The `limit` passed, when it was outside the range from 1 to 200 |\n| `meta.appliedLimit` | number | The `limit` applied — only when it was clamped to a bound |\n\n## Response example\n\n```json\n{\n  \"success\": true,\n  \"data\": [\n    {\n      \"id\": 7,\n      \"active\": true,\n      \"name\": \"Anna Grey\",\n      \"firstName\": \"Anna\",\n      \"lastName\": \"Grey\",\n      \"workPosition\": \"Analyst\",\n      \"color\": \"#83c3f7\",\n      \"avatar\": \"\",\n      \"gender\": \"F\",\n      \"birthday\": \"\",\n      \"extranet\": false,\n      \"network\": false,\n      \"bot\": false,\n      \"connector\": false,\n      \"status\": \"away\",\n      \"idle\": false,\n      \"lastActivityDate\": \"2026-09-20T10:00:00+00:00\",\n      \"absent\": false,\n      \"departments\": [1],\n      \"type\": \"user\"\n    }\n  ]\n}\n```\n\n## Error response example\n\n400 — `order` without `sort`:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"INVALID_PARAMS\",\n    \"message\": \"`order` sets the direction of `sort` and is accepted only together with it.\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|---------|\n| 400 | `INVALID_PARAMS` | A parameter other than `limit`, `sort` or `order`, a repeated parameter, a non-numeric `limit`, a `sort` or `order` value outside the allowed values, or `order` without `sort`. 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 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`. A missing chat lands here with the code `CHAT_NOT_FOUND` |\n| 502 | `ME_ALIAS_RESOLUTION_FAILED` | The user could not be resolved for the `me` alias |\n\nThe full list of common API errors — [Errors](\u002Fdocs\u002Ferrors).\n\n## Known specifics\n\n**Reading may make you a member.** If the chat allows auto-join, Bitrix24 may add the caller as a member. A `READONLY` key may perform this read 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 read does not mark messages as read. The user's Bitrix24 access and the `im` scope still apply.\n\n## See also\n\n- [List members](\u002Fdocs\u002Fchats\u002Fmembers\u002Flist)\n- [Chat members as entities](\u002Fdocs\u002Fchats\u002Fmembers\u002Fmember-entities)\n- [Chat members](\u002Fdocs\u002Fchats\u002Fmembers)\n","2026-10-15",{},1794739543456]