[{"data":1,"prerenderedAt":7},["ShallowReactive",2],{"docs-entities\u002Ftasks\u002Flist":3,"docs-tabs-entities\u002Ftasks\u002Flist":6},{"content":4,"lastmod":5},"\n## List tasks\n\n`GET \u002Fv1\u002Ftasks`\n\nReturns a list of tasks in your Bitrix24 account with support for filtering, sorting, and auto-pagination.\n\n## Parameters\n\n| Parameter | Type | Default | Description |\n|----------|-----|-----------|---------|\n| `limit` | number | `50` | Number of records (up to 5000). When `limit > 50`, the API automatically requests multiple pages |\n| `offset` | number | `0` | Skip N records. When `offset > 0`, `limit ≤ 500` is recommended |\n| `select` | string | — | Field selection: `?select=id,title,status,responsibleId` |\n| `sort` | string | — | Sorting via the short syntax: `?sort=-id`, the minus means descending |\n| `order` | object | `id desc` | Sorting: `?order[id]=desc`, `?order[createdDate]=desc` |\n| `filter` | object | — | Filtering by the fields from `GET \u002Fv1\u002Ftasks\u002Ffields`.\u003Cbr>[Filtering syntax](\u002Fdocs\u002Ffiltering). Example: `?filter[status]=2&filter[responsibleId]=1` |\n| `withTotal` | string | — | Whether you need the count: `true` or `false`. `false` — remove the count from the response; this is the only guaranteed way to remove `meta.total`. Above a `limit` of 50 the platform still needs the count to plan its page requests, so the parameter removes the number, not the load. Without the parameter: the API key setting, then the platform default. [Paging and counts](\u002Fdocs\u002Fentity-api#paging-and-record-counts) |\n\n> **Which dates are filterable.** B24 `tasks.task.list` supports filters by `createdDate`, `changedDate`, `closedDate`, `deadline`, `dateStart`. The fields `statusChangedDate` and `activityDate` are **not filterable** on the Bitrix24 side (they are not in the method's list of filterable fields) — such a filter is silently ignored; use `changedDate` as the closest substitute. A filter on `timeSpentInLogs` is silently ignored the same way — you cannot narrow a selection by the time actually spent, and the sum over a selection comes from [aggregation](.\u002Faggregate.md). Participants and observers can each be filtered by only one user at a time: `?filter[accomplices]=25`, `?filter[auditors]=25`; tags — `?filter[tags]=tag`.\n\n> **`status` vs `realStatus`.** `filter[status]` in Bitrix24 is a **virtual (meta) filter**: values `−1` (overdue), `−2` (unviewed), `−3` (almost overdue) — not the number from the `status` field of the response — so `filter[status]=2` will not return every task with status `2`: this virtual filter assigns exactly one value to each task, and those marked `−1`, `−2` or `−3` fall outside the condition. To filter and sort by the actual status, use `realStatus`: `?filter[realStatus]=2` (pending), `?filter[realStatus]=5` (completed), `?sort=realStatus`. The `realStatus` value matches the `status` field in the response.\n\n> **`meta.total` does not arrive on every call.** When `limit` is at most 50 and `offset` is zero, the count does not have to be requested: if the page came back shorter than `limit`, `meta.total` still arrives with the exact number — the collection ended on that page (an empty result gives `0`); if the page came back full, the field is absent. When `limit` is above 50, `meta.total` arrives — the count runs only where it cannot be avoided — and an explicit `withTotal=false` removes it there too. Check whether the field is present in a given response, and page by `meta.hasMore`.\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl -g \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Ftasks?limit=10&filter[status]=2&order[id]=desc\" \\\n  -H \"X-Api-Key: YOUR_API_KEY\"\n```\n\n### curl — OAuth application\n\n```bash\ncurl -g \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Ftasks?limit=10&filter[status]=2&order[id]=desc\" \\\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 url = 'https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Ftasks?limit=10&filter[status]=2&order[id]=desc'\nconst res = await fetch(url, {\n  headers: {\n    'X-Api-Key': 'YOUR_API_KEY',\n  },\n})\n\nconst { success, data, meta } = await res.json()\nconsole.log(`Received ${data.length} of ${meta.total} tasks`)\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst url = 'https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Ftasks?limit=10&filter[status]=2&order[id]=desc'\nconst res = await fetch(url, {\n  headers: {\n    'X-Api-Key': 'YOUR_APP_KEY',\n    'Authorization': 'Bearer USER_SESSION_TOKEN',\n  },\n})\n\nconst { success, data, meta } = await res.json()\n```\n\n## Response fields\n\n| Field | Type | Description |\n|------|-----|---------|\n| `success` | boolean | Always `true` on success |\n| `data` | array | Array of tasks (all fields — see [Task fields](.\u002Ffields.md)) |\n| `meta.total` | number | Total number of records matching the filter. An optional field — see the note above |\n| `meta.hasMore` | boolean | Whether there are more records beyond `limit` |\n\nThe card URL of any task from the `data` array is built from its `id` and the employee ID:\n\n```\nhttps:\u002F\u002F\u003Cportal>.bitrix24.com\u002Fcompany\u002Fpersonal\u002Fuser\u002F\u003CresponsibleId>\u002Ftasks\u002Ftask\u002Fview\u002F\u003Cid>\u002F\n```\n\n`\u003CresponsibleId>` — the responsible person's ID (the `responsibleId` field of each element): the task opens in their personal workspace. The `user\u002F\u003C...>` segment determines whose workspace the tasks page is shown in — substitute the ID of the employee you need, for example the current one. `\u003Cportal>` — your Bitrix24 account domain. Access is limited by the employee's permissions in Bitrix24.\n\n## Response example\n\n```json\n{\n  \"success\": true,\n  \"data\": [\n    {\n      \"id\": 289,\n      \"title\": \"Prepare the quarterly report\",\n      \"status\": 2,\n      \"priority\": 1,\n      \"responsibleId\": 79,\n      \"createdBy\": 99,\n      \"createdDate\": \"2026-05-12T09:11:18.000Z\",\n      \"deadline\": \"2026-05-19T18:00:00.000Z\",\n      \"groupId\": 0,\n      \"accomplices\": [],\n      \"auditors\": [],\n      \"tags\": {},\n      \"notViewed\": false,\n      \"chatId\": 3567,\n      \"creator\": {\n        \"id\": \"99\",\n        \"name\": \"John Smith\",\n        \"link\": \"\u002Fcompany\u002Fpersonal\u002Fuser\u002F99\u002F\"\n      },\n      \"responsible\": {\n        \"id\": \"79\",\n        \"name\": \"Jane Doe\",\n        \"link\": \"\u002Fcompany\u002Fpersonal\u002Fuser\u002F79\u002F\"\n      }\n    }\n  ],\n  \"meta\": {\n    \"total\": 184,\n    \"hasMore\": true\n  }\n}\n```\n\n## Error response example\n\n403 — no scope:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"SCOPE_DENIED\",\n    \"message\": \"This endpoint requires 'tasks' scope\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|---------|\n| 403 | `SCOPE_DENIED` | The API key does not have the `tasks` scope |\n| 401 | `TOKEN_MISSING` | The API key has no configured tokens |\n| 401 | `MISSING_API_KEY` | The `X-Api-Key` header was not passed |\n| 401 | `INVALID_API_KEY` | The key is not recognized — no such key exists on the platform |\n| 429 | `RATE_LIMITED` | Rate limit exceeded: 300 requests per minute per portal. All API keys of the portal share one limit. The current limit is returned in the `x-ratelimit-limit` header. Retry after the delay in the `Retry-After` header |\n\nFor the full list of common API errors, see [Errors](\u002Fdocs\u002Ferrors).\n\n## Known specifics\n\n**When to switch to `POST \u002Fv1\u002Ftasks\u002Fsearch`.** If a request has many filter conditions or you need to export records over a large date range, choose `POST \u002Fv1\u002Ftasks\u002Fsearch` — parameters are passed in the body, and the request can be split automatically into time windows for result sets over 5000 records. See [Search tasks](.\u002Fsearch.md).\n\n**Type coercion works at the top level and does not descend into objects.** The card fields (`creator`, `responsible`, `group`, `accomplicesData`, `auditorsData`) are declared as objects and arrive from Bitrix24 as-is — the values inside them stay exactly as the Bitrix24 account returned them, including `creator.id` as a string (`\"99\"`). That is not the same as the top-level `createdBy`, which arrives as a number. Convert via `Number()` for arithmetic on a nested identifier.\n\n**Value types match the schema.** Fields declared as numbers in the [schema](.\u002Ffields.md) (`id`, `status`, `priority`, `responsibleId`, `createdBy`, `groupId`, `chatId`, and similar) arrive as numbers; yes\u002Fno flags arrive as `true`\u002F`false`; empty `tags`, `group`, `accomplicesData` and `auditorsData` arrive as an empty object `{}`. Converting via `Number(value)` is no longer needed. These values used to arrive as strings — if your code compares them against a string (`status === \"2\"`), it needs updating.\n\n## See also\n\n- [Get task](.\u002Fget.md)\n- [Search tasks](.\u002Fsearch.md)\n- [Task fields](.\u002Ffields.md)\n- [Aggregate tasks](.\u002Faggregate.md)\n- [Filtering syntax](\u002Fdocs\u002Ffiltering)\n- [Batch](\u002Fdocs\u002Fbatch)\n- [Limits and optimization](\u002Fdocs\u002Foptimization)\n","2026-10-23",{},1794739435471]