[{"data":1,"prerenderedAt":17},["ShallowReactive",2],{"docs-workday\u002Fwork-reports":3,"docs-tabs-workday\u002Fwork-reports":6},{"content":4,"lastmod":5},"# Work reports\n\nAn employee's work report for a period: the employee creates and submits the report, and the manager reads their subordinates' reports and marks them.\n\nReport contents — [Report fields](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Ffields).\n\n**Scope:** `timeman` | **Base URL:** `https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1` | **Authorization:** `X-Api-Key`\n\n- [Report comments](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Fcomments) — `GET \u002Fv1\u002Fworkday\u002Fwork-reports\u002F:id\u002Fcomments`\n\n## Operations\n\n- [List work reports](.\u002Fwork-reports\u002Flist.md) — `GET \u002Fv1\u002Fworkday\u002Fwork-reports`\n- [Subordinate work reports](.\u002Fwork-reports\u002Fsubordinates.md) — `GET \u002Fv1\u002Fworkday\u002Fwork-reports\u002Fsubordinates`\n- [Read a work report](.\u002Fwork-reports\u002Fget.md) — `GET \u002Fv1\u002Fworkday\u002Fwork-reports\u002F:id`\n- [Create a work report](.\u002Fwork-reports\u002Fcreate.md) — `POST \u002Fv1\u002Fworkday\u002Fwork-reports`\n- [Update a work report](.\u002Fwork-reports\u002Fupdate.md) — `PATCH \u002Fv1\u002Fworkday\u002Fwork-reports\u002F:id`\n- [Send a work report](.\u002Fwork-reports\u002Fsend.md) — `POST \u002Fv1\u002Fworkday\u002Fwork-reports\u002F:id\u002Fsend`\n- [Submit a work report](.\u002Fwork-reports\u002Fsubmit.md) — `POST \u002Fv1\u002Fworkday\u002Fwork-reports\u002Fsubmit`\n- [Approve a work report](.\u002Fwork-reports\u002Fapprove.md) — `POST \u002Fv1\u002Fworkday\u002Fwork-reports\u002F:id\u002Fapprove`\n- [Reject a work report](.\u002Fwork-reports\u002Freject.md) — `POST \u002Fv1\u002Fworkday\u002Fwork-reports\u002F:id\u002Freject`\n- [Disapprove a work report](.\u002Fwork-reports\u002Fdisapprove.md) — `POST \u002Fv1\u002Fworkday\u002Fwork-reports\u002F:id\u002Fdisapprove`\n\n## Access\n\nBitrix24 checks the credential owner's permissions: for a personal key, that is the key owner; for an app key, the user whose session token is passed in `Authorization`. A `READONLY` key can read reports but cannot create, edit, submit, or mark them. Each read method accepts up to 30 requests per minute per key-and-user pair and returns `429 RATE_LIMITED` beyond that.\n\n## Typical scenario\n\nEmployee:\n\n1. Create a report for a period: [`POST \u002Fv1\u002Fworkday\u002Fwork-reports`](.\u002Fwork-reports\u002Fcreate.md). Edit it: [`PATCH \u002Fv1\u002Fworkday\u002Fwork-reports\u002F:id`](.\u002Fwork-reports\u002Fupdate.md).\n2. Submit the created report: [`POST \u002Fv1\u002Fworkday\u002Fwork-reports\u002F:id\u002Fsend`](.\u002Fwork-reports\u002Fsend.md). To create and submit a report in one call: [`POST \u002Fv1\u002Fworkday\u002Fwork-reports\u002Fsubmit`](.\u002Fwork-reports\u002Fsubmit.md) without `reportId`.\n\nManager:\n\n1. Get subordinates' reports: [`GET \u002Fv1\u002Fworkday\u002Fwork-reports\u002Fsubordinates`](.\u002Fwork-reports\u002Fsubordinates.md).\n2. Mark a report by its `id`: approve it with [`approve`](.\u002Fwork-reports\u002Fapprove.md), give it a neutral mark with [`reject`](.\u002Fwork-reports\u002Freject.md), or a negative one with [`disapprove`](.\u002Fwork-reports\u002Fdisapprove.md).\n\n## See also\n\n- [Report fields](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Ffields)\n- [Daily reports](\u002Fdocs\u002Fworkday\u002Fdaily-reports)\n- [Workday](\u002Fdocs\u002Fworkday)\n","2026-11-12",{"work-reports\u002Flist.md":7,"work-reports\u002Fsubordinates.md":8,"work-reports\u002Fget.md":9,"work-reports\u002Fcreate.md":10,"work-reports\u002Fupdate.md":11,"work-reports\u002Fsend.md":12,"work-reports\u002Fsubmit.md":13,"work-reports\u002Fapprove.md":14,"work-reports\u002Freject.md":15,"work-reports\u002Fdisapprove.md":16},"## List work reports\n\n`GET \u002Fv1\u002Fworkday\u002Fwork-reports`\n\nReturns an employee's work reports, filtered by period and paginated.\n\nRequires the `timeman` scope. Bitrix24 checks the credential owner’s permissions. READONLY keys can read reports and cannot write them.\n\n## Parameters\n\n| Parameter | Type | Required | Default | Description |\n|----------|-----|:-----:|-----------|----------|\n| `userId` (query) | integer | yes | — | ID of the employee whose reports you need. List: [`GET \u002Fv1\u002Fusers`](\u002Fdocs\u002Fentities\u002Fusers\u002Flist) |\n| `activeOnly` (query) | boolean | no | — | `true` returns submitted reports only |\n| `dateFrom` (query) | string | no | — | Period start in ISO 8601 format with a time zone. Reports whose period overlaps the given one are returned; the boundaries are inclusive |\n| `dateTo` (query) | string | no | — | Period end in the same format |\n| `limit` (query) | integer | no | `50` | How many reports to return, from 1 to 50 |\n| `offset` (query) | integer | no | `0` | How many reports to skip. Cannot be combined with `page` |\n| `page` (query) | integer | no | `1` | Page number, with `limit` reports per page. Cannot be combined with `offset` |\n| `order` (query) | string | no | `{\"id\":\"desc\"}` | Sort order — a JSON object with `asc` or `desc` directions, for example `{\"id\":\"asc\"}` |\n| `select` (query) | string | no | — | Comma-separated report fields. For the list, see [Report fields](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Ffields) |\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fworkday\u002Fwork-reports?userId=101\" \\\n  -H \"X-Api-Key: YOUR_API_KEY\"\n```\n\n### curl — OAuth application\n\n```bash\ncurl \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fworkday\u002Fwork-reports?userId=101\" \\\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\u002Fworkday\u002Fwork-reports?userId=101', {\n  headers: {\n    'X-Api-Key': 'YOUR_API_KEY',\n  },\n})\nconst { data, meta } = await res.json()\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fworkday\u002Fwork-reports?userId=101', {\n  headers: {\n    'X-Api-Key': 'YOUR_APP_KEY',\n    'Authorization': 'Bearer USER_SESSION_TOKEN',\n  },\n})\nconst { data, meta } = await res.json()\n```\n\n## Response fields\n\n| Field | Type | Description |\n|------|-----|----------|\n| `success` | boolean | `true` when the request succeeds |\n| `data` | array | Array of reports. For the fields of each report, see [Report fields](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Ffields) |\n| `meta.limit` | integer | Page size |\n| `meta.offset` | integer | How many reports were skipped |\n| `meta.hasMore` | boolean | `true` when the page holds `limit` reports and more may follow |\n\n## Response example\n\nThe main report fields are shown. For the full list, see [Report fields](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Ffields):\n\n```json\n{\n  \"success\": true,\n  \"data\": [\n    {\n      \"id\": 145,\n      \"userId\": 101,\n      \"active\": false,\n      \"reportType\": \"day\",\n      \"reportDate\": \"2026-10-06T18:33:06.000Z\",\n      \"dateFrom\": \"2026-10-06T21:00:00.000Z\",\n      \"dateTo\": \"2026-10-06T21:00:00.000Z\",\n      \"report\": \"Sprint summary\",\n      \"type\": \"REPORT\",\n      \"mark\": \"N\",\n      \"approve\": \"N\"\n    },\n    {\n      \"id\": 143,\n      \"userId\": 101,\n      \"active\": false,\n      \"reportType\": \"day\",\n      \"reportDate\": \"2026-10-06T18:22:40.000Z\",\n      \"dateFrom\": \"2026-10-05T21:00:00.000Z\",\n      \"dateTo\": \"2026-10-05T21:00:00.000Z\",\n      \"report\": \"Weekly report\",\n      \"type\": \"REPORT\",\n      \"mark\": \"N\",\n      \"approve\": \"N\"\n    }\n  ],\n  \"meta\": {\n    \"limit\": 50,\n    \"offset\": 0,\n    \"hasMore\": false\n  }\n}\n```\n\n## Error response example\n\n400 — `userId` is missing:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"INVALID_PARAMS\",\n    \"message\": \"Expected a positive integer\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|----------|\n| 400 | `WORKDAY_REPORT_LIMIT_EXCEEDED` | `limit` is greater than 50 |\n| 400 | `INVALID_PARAMS` | `userId` is missing, `offset` and `page` are both passed, `select` has an unknown field, a date is invalid, or an unknown parameter is passed |\n| 403 | `BITRIX_ACCESS_DENIED` | The credential owner lacks Bitrix24 permissions for this employee's reports |\n| 409 | `TIMEMAN_MODULE_NOT_ENABLED` | Time Management is not available on this portal |\n| 422 | `BITRIX_ERROR` | Bitrix24 refused the operation |\n| 502 | `BITRIX_UNAVAILABLE` | Bitrix24 is unavailable or returned a response of an unexpected shape |\n| 401 | `MISSING_API_KEY` | The `X-Api-Key` header was not passed |\n| 401 | `TOKEN_MISSING` | An app key was sent without a session token in `Authorization: Bearer` |\n| 401 | `INVALID_SESSION` | The session token is invalid or has expired |\n| 403 | `SCOPE_DENIED` | The key lacks the `timeman` scope |\n| 429 | `RATE_LIMITED` | The report read limit or the general request limit was exceeded |\n\nThe full list of common API errors — [Errors](\u002Fdocs\u002Ferrors).\n\n## Known specifics\n\n- **`select` keeps only the listed fields in each report.** `id` is always returned, even when it is not in the list.\n- **Only `id` sets the order.** Other fields in `order` apply after `id`, so they do not change the order of the results.\n- **`dateFrom` and `dateTo` must be strictly later than `1970-01-01T00:00:00Z`.** An earlier date, or that exact timestamp, returns `400 INVALID_PARAMS`.\n\n## See also\n\n- [Create a work report](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Fcreate)\n- [Submit a work report](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Fsubmit)\n- [Work reports](\u002Fdocs\u002Fworkday\u002Fwork-reports)\n- [Daily reports](\u002Fdocs\u002Fworkday\u002Fdaily-reports)\n- [Workday](\u002Fdocs\u002Fworkday)\n","## Subordinate work reports\n\n`GET \u002Fv1\u002Fworkday\u002Fwork-reports\u002Fsubordinates`\n\nReturns the submitted work reports of the credential owner and of the employees whose time records the owner can read. Useful for a manager reviewing the team's reports.\n\nRequires the `timeman` scope and the credential owner's Bitrix24 right to read the time records of subordinates or of all employees. With the right to read the time records of all employees, the reports of the whole company are returned. READONLY keys can read reports.\n\n## Parameters\n\n| Parameter | Type | Required | Default | Description |\n|----------|-----|:-----:|-----------|----------|\n| `userId` (query) | integer | no | — | Employee ID — return only this employee's reports. List: [`GET \u002Fv1\u002Fusers`](\u002Fdocs\u002Fentities\u002Fusers\u002Flist) |\n| `userIds` (query) | string | no | — | Comma-separated employee IDs, for example `103,105`. If `userId` is also passed, the reports of all listed employees are returned. List: [`GET \u002Fv1\u002Fusers`](\u002Fdocs\u002Fentities\u002Fusers\u002Flist) |\n| `activeOnly` (query) | boolean | no | — | Accepted but does not change the result: only submitted reports are returned |\n| `dateFrom` (query) | string | no | — | Period start in ISO 8601 format with a time zone. Reports whose period overlaps the given one are returned; the boundaries are inclusive |\n| `dateTo` (query) | string | no | — | Period end in the same format |\n| `limit` (query) | integer | no | `5` | How many employees to return, from 1 to 50 |\n| `offset` (query) | integer | no | `0` | How many employees to skip. Cannot be combined with `page` |\n| `page` (query) | integer | no | `1` | Page number, with `limit` employees per page. Cannot be combined with `offset` |\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fworkday\u002Fwork-reports\u002Fsubordinates?userIds=103,105\" \\\n  -H \"X-Api-Key: YOUR_API_KEY\"\n```\n\n### curl — OAuth application\n\n```bash\ncurl \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fworkday\u002Fwork-reports\u002Fsubordinates?userIds=103,105\" \\\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\u002Fworkday\u002Fwork-reports\u002Fsubordinates?userIds=103,105', {\n  headers: {\n    'X-Api-Key': 'YOUR_API_KEY',\n  },\n})\nconst { data, meta } = await res.json()\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fworkday\u002Fwork-reports\u002Fsubordinates?userIds=103,105', {\n  headers: {\n    'X-Api-Key': 'YOUR_APP_KEY',\n    'Authorization': 'Bearer USER_SESSION_TOKEN',\n  },\n})\nconst { data, meta } = await res.json()\n```\n\n## Response fields\n\n| Field | Type | Description |\n|------|-----|----------|\n| `success` | boolean | `true` when the request succeeds |\n| `data` | array | Employees with submitted reports. An employee without matching reports is not included. The credential owner comes first if they have matching reports |\n| `data[].userId` | integer | Employee ID. List: [`GET \u002Fv1\u002Fusers`](\u002Fdocs\u002Fentities\u002Fusers\u002Flist) |\n| `data[].user` | object \\| null | The employee |\n| `data[].user.id` | integer | Employee ID, the same as `userId` |\n| `data[].user.name` | string | Employee's first and last name |\n| `data[].user.photo` | string \\| null | Profile photo URL |\n| `data[].reports` | array | The employee's submitted reports in descending `id` order. For the report structure, see [Report fields](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Ffields) |\n| `meta.offset` | integer | How many employees were skipped |\n| `meta.limit` | integer | How many employees fit on a page |\n| `meta.hasMore` | boolean | `true` if more employees follow this page |\n| `meta.nextOffset` | integer \\| null | The `offset` value for the next page, or `null` if there are no more pages |\n| `meta.paginationUnit` | string | Always `users`: `limit` and `offset` count employees, not reports |\n\n## Response example\n\nThe main report fields are shown. For the full list, see [Report fields](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Ffields):\n\n```json\n{\n  \"success\": true,\n  \"data\": [\n    {\n      \"userId\": 103,\n      \"user\": {\n        \"id\": 103,\n        \"name\": \"Anna Smith\",\n        \"photo\": null\n      },\n      \"reports\": [\n        {\n          \"id\": 79,\n          \"userId\": 103,\n          \"active\": true,\n          \"reportType\": \"week\",\n          \"reportDate\": \"2023-03-02T10:39:37.000Z\",\n          \"dateFrom\": \"2023-01-15T21:00:00.000Z\",\n          \"dateTo\": \"2023-01-21T21:00:00.000Z\",\n          \"report\": \"Hi :)\",\n          \"type\": \"REPORT\",\n          \"mark\": \"G\",\n          \"approve\": \"Y\"\n        }\n      ]\n    },\n    {\n      \"userId\": 105,\n      \"user\": {\n        \"id\": 105,\n        \"name\": \"John Brown\",\n        \"photo\": null\n      },\n      \"reports\": [\n        {\n          \"id\": 115,\n          \"userId\": 105,\n          \"active\": true,\n          \"reportType\": \"week\",\n          \"reportDate\": \"2024-02-14T11:34:24.000Z\",\n          \"dateFrom\": \"2024-02-04T21:00:00.000Z\",\n          \"dateTo\": \"2024-02-10T21:00:00.000Z\",\n          \"report\": \"\",\n          \"type\": \"REPORT\",\n          \"mark\": \"X\",\n          \"approve\": \"N\"\n        },\n        {\n          \"id\": 111,\n          \"userId\": 105,\n          \"active\": true,\n          \"reportType\": \"week\",\n          \"reportDate\": \"2024-01-26T14:20:50.000Z\",\n          \"dateFrom\": \"2024-01-21T21:00:00.000Z\",\n          \"dateTo\": \"2024-01-27T21:00:00.000Z\",\n          \"report\": \"\",\n          \"type\": \"REPORT\",\n          \"mark\": \"X\",\n          \"approve\": \"N\"\n        }\n      ]\n    }\n  ],\n  \"meta\": {\n    \"offset\": 0,\n    \"limit\": 5,\n    \"hasMore\": false,\n    \"nextOffset\": null,\n    \"paginationUnit\": \"users\"\n  }\n}\n```\n\n## Error response example\n\n400 — `limit` is greater than 50:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"WORKDAY_REPORT_LIMIT_EXCEEDED\",\n    \"message\": \"Report list limit must be between 1 and 50\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|----------|\n| 400 | `WORKDAY_REPORT_LIMIT_EXCEEDED` | `limit` is greater than 50 |\n| 400 | `INVALID_PARAMS` | `userId`, `limit`, or `page` is not a positive integer; `userIds` is not a comma-separated list of positive integers; `offset` is not a non-negative integer; `offset` and `page` were passed together; `activeOnly` is not `true`, `false`, `1`, or `0`; a date has no time zone, does not exist, or is not later than `1970-01-01T00:00:00Z`; an unknown parameter is passed, such as `order` or `select`; a parameter is passed twice |\n| 403 | `BITRIX_ACCESS_DENIED` | The credential owner lacks the right to read the time records of subordinates or of all employees |\n| 409 | `TIMEMAN_MODULE_NOT_ENABLED` | Time Management is not available on this portal |\n| 422 | `BITRIX_ERROR` | Bitrix24 refused the operation |\n| 502 | `BITRIX_UNAVAILABLE` | Bitrix24 is unavailable or returned a response of an unexpected shape |\n| 401 | `MISSING_API_KEY` | The `X-Api-Key` header was not passed |\n| 401 | `TOKEN_MISSING` | An app key was sent without a session token in `Authorization: Bearer` |\n| 401 | `INVALID_SESSION` | The session token is invalid or has expired |\n| 403 | `SCOPE_DENIED` | The key lacks the `timeman` scope |\n| 429 | `RATE_LIMITED` | The report read limit (30 requests per minute per key–user pair) or the general request limit was exceeded. The effective report read limit is in the `x-ratelimit-limit` header |\n\nFor the full list of common API errors, see [Errors](\u002Fdocs\u002Ferrors).\n\n## See also\n\n- [List work reports](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Flist)\n- [Report fields](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Ffields)\n- [Work reports](\u002Fdocs\u002Fworkday\u002Fwork-reports)\n- [Daily reports](\u002Fdocs\u002Fworkday\u002Fdaily-reports)\n- [Workday](\u002Fdocs\u002Fworkday)\n","## Read a work report\n\n`GET \u002Fv1\u002Fworkday\u002Fwork-reports\u002F:id`\n\nReturns a single work report by the report ID and the ID of the employee it belongs to.\n\nRequires the `timeman` scope. Bitrix24 checks the credential owner’s permissions. READONLY keys can read reports and cannot write them.\n\n## Parameters\n\n| Parameter | Type | Required | Default | Description |\n|----------|-----|:-----:|-----------|----------|\n| `id` (path) | integer | yes | — | Report ID. List: [`GET \u002Fv1\u002Fworkday\u002Fwork-reports`](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Flist) |\n| `userId` (query) | integer | yes | — | ID of the employee the report belongs to — the `userId` field of the report. List: [`GET \u002Fv1\u002Fusers`](\u002Fdocs\u002Fentities\u002Fusers\u002Flist). Any other ID returns `403 BITRIX_ACCESS_DENIED` |\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fworkday\u002Fwork-reports\u002F143?userId=101\" \\\n  -H \"X-Api-Key: YOUR_API_KEY\"\n```\n\n### curl — OAuth application\n\n```bash\ncurl \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fworkday\u002Fwork-reports\u002F143?userId=101\" \\\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\u002Fworkday\u002Fwork-reports\u002F143?userId=101', {\n  headers: {\n    'X-Api-Key': 'YOUR_API_KEY',\n  },\n})\nconst { data } = await res.json()\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fworkday\u002Fwork-reports\u002F143?userId=101', {\n  headers: {\n    'X-Api-Key': 'YOUR_APP_KEY',\n    'Authorization': 'Bearer USER_SESSION_TOKEN',\n  },\n})\nconst { data } = await res.json()\n```\n\n## Response fields\n\n| Field | Type | Description |\n|------|-----|----------|\n| `success` | boolean | `true` when the request succeeds |\n| `data` | object | The report. All fields — [Report fields](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Ffields) |\n\n## Response example\n\nThe main report fields are shown. For the full list, see [Report fields](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Ffields):\n\n```json\n{\n  \"success\": true,\n  \"data\": {\n    \"id\": 143,\n    \"userId\": 101,\n    \"active\": true,\n    \"reportType\": \"day\",\n    \"reportDate\": \"2026-10-06T18:22:40.000Z\",\n    \"dateFrom\": \"2026-10-05T21:00:00.000Z\",\n    \"dateTo\": \"2026-10-05T21:00:00.000Z\",\n    \"report\": \"Weekly report\",\n    \"type\": \"REPORT\",\n    \"mark\": \"N\",\n    \"approve\": \"Y\"\n  }\n}\n```\n\n## Error response example\n\n404 — no report with this `id` exists:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"ENTITY_NOT_FOUND\",\n    \"message\": \"Report not found.\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|----------|\n| 400 | `INVALID_PARAMS` | `userId` is missing, `id` or `userId` is not a positive integer, an unknown parameter is passed, or a parameter is passed twice |\n| 404 | `ENTITY_NOT_FOUND` | No report with this `id` exists |\n| 403 | `BITRIX_ACCESS_DENIED` | `userId` does not match the employee the report belongs to, or the credential owner lacks Bitrix24 permissions for this employee's reports |\n| 409 | `TIMEMAN_MODULE_NOT_ENABLED` | Time Management is not available on this portal |\n| 422 | `BITRIX_ERROR` | Bitrix24 refused the operation |\n| 502 | `BITRIX_UNAVAILABLE` | Bitrix24 is unavailable or returned a response of an unexpected shape |\n| 401 | `MISSING_API_KEY` | The `X-Api-Key` header was not passed |\n| 401 | `TOKEN_MISSING` | An app key was sent without a session token in `Authorization: Bearer` |\n| 401 | `INVALID_SESSION` | The session token is invalid or has expired |\n| 403 | `SCOPE_DENIED` | The key lacks the `timeman` scope |\n| 429 | `RATE_LIMITED` | The report read limit or the general request limit was exceeded |\n\nThe full list of common API errors — [Errors](\u002Fdocs\u002Ferrors).\n\n## See also\n\n- [List work reports](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Flist)\n- [Update a work report](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Fupdate)\n- [Submit a work report](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Fsubmit)\n- [Work reports](\u002Fdocs\u002Fworkday\u002Fwork-reports)\n- [Daily reports](\u002Fdocs\u002Fworkday\u002Fdaily-reports)\n- [Workday](\u002Fdocs\u002Fworkday)\n","## Create a work report\n\n`POST \u002Fv1\u002Fworkday\u002Fwork-reports`\n\nCreates an employee's work report for a period. The new report is not submitted; submit it with a separate call.\n\nRequires the `timeman` scope. Bitrix24 checks the credential owner’s permissions. READONLY keys can read reports and cannot write them.\n\n## Request fields (body)\n\n| Field | Type | Required | Description |\n|------|-----|:-----:|----------|\n| `userId` | integer | yes | ID of the employee the report belongs to. List: [`GET \u002Fv1\u002Fusers`](\u002Fdocs\u002Fentities\u002Fusers\u002Flist) |\n| `reportText` | string \\| null | no | Report text. Returned as `report` and `reportPlain` |\n| `reportExtended` | string \\| null | no | Additional report text. Returned as `reportExtended` |\n| `plansText` | string \\| null | no | Plans. Returned as `plans` |\n| `type` | string \\| null | no | Report type: `REPORT`, `AI_REPORT`, `ROBOT_REPORT`, `AI_DAY_PLAN`, or `ROBOT_DAY_PLAN`. If omitted or set to any other value, `REPORT` is used |\n| `dateFrom` | string \\| null | no | Start of the report period in ISO 8601 format with a time zone. The time is dropped; only the date is stored |\n| `dateTo` | string \\| null | no | End of the report period in the same format. The time is dropped; only the date is stored |\n| `tasks` | array \\| null | no | Tasks in the report |\n| `tasks[].id` | integer | yes | Task ID. List: [`GET \u002Fv1\u002Ftasks`](\u002Fdocs\u002Fentities\u002Ftasks\u002Flist) |\n| `tasks[].time` | number | no | Time spent on the task, in seconds. The fractional part is dropped |\n| `tasks[].title` | string | no | Task title in the report |\n| `events` | array \\| null | no | Calendar events in the report |\n| `events[].id` | integer | yes | Event ID. List: [`GET \u002Fv1\u002Fcalendar-events`](\u002Fdocs\u002Fentities\u002Fcalendar-events\u002Flist) |\n| `events[].ownerId` | integer | no | ID of the event owner. List: [`GET \u002Fv1\u002Fusers`](\u002Fdocs\u002Fentities\u002Fusers\u002Flist) |\n| `events[].title` | string | no | Event title in the report |\n| `autoFillDailyReports` | boolean | no | Defaults to `false` |\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl -X POST https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fworkday\u002Fwork-reports \\\n  -H \"X-Api-Key: YOUR_API_KEY\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{ \"userId\": 101, \"reportText\": \"Weekly report\" }'\n```\n\n### curl — OAuth application\n\n```bash\ncurl -X POST https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fworkday\u002Fwork-reports \\\n  -H \"X-Api-Key: YOUR_APP_KEY\" \\\n  -H \"Authorization: Bearer USER_SESSION_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{ \"userId\": 101, \"reportText\": \"Weekly report\" }'\n```\n\n### JavaScript — personal key\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fworkday\u002Fwork-reports', {\n  method: 'POST',\n  headers: {\n    'X-Api-Key': 'YOUR_API_KEY',\n    'Content-Type': 'application\u002Fjson',\n  },\n  body: JSON.stringify({\n    userId: 101,\n    reportText: 'Weekly report',\n  }),\n})\nconst { data } = await res.json()\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fworkday\u002Fwork-reports', {\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({\n    userId: 101,\n    reportText: 'Weekly report',\n  }),\n})\nconst { data } = await res.json()\n```\n\n## Response fields\n\n| Field | Type | Description |\n|------|-----|----------|\n| `success` | boolean | `true` when the report is created |\n| `data` | object | The created report. All fields — [Report fields](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Ffields) |\n\n## Response example\n\nThe main report fields are shown. For the full list, see [Report fields](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Ffields):\n\n```json\n{\n  \"success\": true,\n  \"data\": {\n    \"id\": 143,\n    \"userId\": 101,\n    \"active\": false,\n    \"reportType\": \"day\",\n    \"reportDate\": \"2026-10-06T18:22:40.000Z\",\n    \"dateFrom\": \"2026-10-05T21:00:00.000Z\",\n    \"dateTo\": \"2026-10-05T21:00:00.000Z\",\n    \"report\": \"Weekly report\",\n    \"type\": \"REPORT\",\n    \"mark\": \"N\",\n    \"approve\": \"N\"\n  }\n}\n```\n\n## Error response example\n\n400 — `userId` is missing:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"INVALID_PARAMS\",\n    \"message\": \"Expected a positive integer\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|----------|\n| 400 | `INVALID_PARAMS` | `userId` is missing, a field has the wrong type, a date has no time zone, or the body contains an unknown field such as `files` |\n| 403 | `BITRIX_ACCESS_DENIED` | The credential owner lacks the required Bitrix24 permissions |\n| 409 | `TIMEMAN_MODULE_NOT_ENABLED` | Time Management is not available on this portal |\n| 422 | `BITRIX_ERROR` | Bitrix24 refused the operation |\n| 502 | `BITRIX_UNAVAILABLE` | Bitrix24 is unavailable or returned a response of an unexpected shape |\n| 401 | `MISSING_API_KEY` | The `X-Api-Key` header was not passed |\n| 401 | `TOKEN_MISSING` | An app key was sent without a session token in `Authorization: Bearer` |\n| 401 | `INVALID_SESSION` | The session token is invalid or has expired |\n| 403 | `WRITE_BLOCKED_READONLY_KEY` | The key is READONLY and cannot create reports |\n| 403 | `SCOPE_DENIED` | The key lacks the `timeman` scope |\n| 429 | `RATE_LIMITED` | The general request limit was exceeded |\n\nThe full list of common API errors — [Errors](\u002Fdocs\u002Ferrors).\n\n## Known specifics\n\n- **The period can shift.** If the period overlaps a report the employee already has, the period start moves to the day after that report. The period chosen when `dateFrom` and `dateTo` are omitted shifts the same way. The resulting period is returned in the `dateFrom` and `dateTo` fields of the response.\n- **The employee and tasks are not checked for existence.** A report is created even with a nonexistent `userId` or `tasks[].id`. Only the credential owner’s permissions are checked.\n\n## See also\n\n- [Submit a work report](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Fsubmit)\n- [List work reports](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Flist)\n- [Work reports](\u002Fdocs\u002Fworkday\u002Fwork-reports)\n- [Daily reports](\u002Fdocs\u002Fworkday\u002Fdaily-reports)\n- [Workday](\u002Fdocs\u002Fworkday)\n","## Update a work report\n\n`PATCH \u002Fv1\u002Fworkday\u002Fwork-reports\u002F:id`\n\nUpdates the specified fields of an employee's work report and leaves the rest unchanged.\n\nRequires the `timeman` scope. Bitrix24 checks the credential owner’s permissions. READONLY keys can read reports and cannot write them.\n\n## Parameters\n\n| Parameter | Type | Required | Default | Description |\n|----------|-----|:-----:|-----------|----------|\n| `id` (path) | integer | yes | — | Report ID. List: [`GET \u002Fv1\u002Fworkday\u002Fwork-reports`](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Flist) |\n\n## Request fields (body)\n\n| Field | Type | Required | Description |\n|------|-----|:-----:|----------|\n| `reportText` | string \\| null | no | Report text. Returned as `report` and `reportPlain`. An empty string clears the text |\n| `reportExtended` | string \\| null | no | Additional report text. Returned as `reportExtended`. An empty string clears the text |\n| `plansText` | string \\| null | no | Plans. Returned as `plans`. An empty string clears the plans |\n| `type` | string \\| null | no | Report type: `REPORT`, `AI_REPORT`, `ROBOT_REPORT`, `AI_DAY_PLAN`, or `ROBOT_DAY_PLAN`. Any other value is stored as `REPORT` |\n| `dateFrom` | string \\| null | no | Start of the report period in ISO 8601 format with a time zone. The time is dropped; only the date is stored |\n| `dateTo` | string \\| null | no | End of the report period in the same format. The time is dropped; only the date is stored |\n| `tasks` | array \\| null | no | Tasks in the report. A new array replaces the whole list, and an empty array clears it |\n| `tasks[].id` | integer | yes | Task ID. List: [`GET \u002Fv1\u002Ftasks`](\u002Fdocs\u002Fentities\u002Ftasks\u002Flist) |\n| `tasks[].time` | number | no | Time spent on the task, in seconds. The fractional part is dropped |\n| `tasks[].title` | string | no | Task title in the report |\n| `events` | array \\| null | no | Calendar events in the report. A new array replaces the whole list, and an empty array clears it |\n| `events[].id` | integer | yes | Event ID. List: [`GET \u002Fv1\u002Fcalendar-events`](\u002Fdocs\u002Fentities\u002Fcalendar-events\u002Flist) |\n| `events[].ownerId` | integer | no | ID of the event owner. List: [`GET \u002Fv1\u002Fusers`](\u002Fdocs\u002Fentities\u002Fusers\u002Flist) |\n| `events[].title` | string | no | Event title in the report |\n\nFields omitted from the body or set to `null` keep their current values. At least one field with a value is required: an empty body or a body with only `null` values returns `400 INVALID_PARAMS`.\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl -X PATCH https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fworkday\u002Fwork-reports\u002F169 \\\n  -H \"X-Api-Key: YOUR_API_KEY\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{ \"reportText\": \"Updated report\" }'\n```\n\n### curl — OAuth application\n\n```bash\ncurl -X PATCH https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fworkday\u002Fwork-reports\u002F169 \\\n  -H \"X-Api-Key: YOUR_APP_KEY\" \\\n  -H \"Authorization: Bearer USER_SESSION_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{ \"reportText\": \"Updated report\" }'\n```\n\n### JavaScript — personal key\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fworkday\u002Fwork-reports\u002F169', {\n  method: 'PATCH',\n  headers: {\n    'X-Api-Key': 'YOUR_API_KEY',\n    'Content-Type': 'application\u002Fjson',\n  },\n  body: JSON.stringify({\n    reportText: 'Updated report',\n  }),\n})\nconst { data } = await res.json()\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fworkday\u002Fwork-reports\u002F169', {\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({\n    reportText: 'Updated report',\n  }),\n})\nconst { data } = await res.json()\n```\n\n## Response fields\n\n| Field | Type | Description |\n|------|-----|----------|\n| `success` | boolean | `true` when the report is updated |\n| `data` | object | The updated report. All fields — [Report fields](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Ffields) |\n\n## Response example\n\nThe main report fields are shown. For the full list, see [Report fields](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Ffields):\n\n```json\n{\n  \"success\": true,\n  \"data\": {\n    \"id\": 169,\n    \"userId\": 101,\n    \"active\": false,\n    \"reportType\": \"day\",\n    \"reportDate\": \"2026-10-06T20:25:34.000Z\",\n    \"dateFrom\": \"2026-10-06T21:00:00.000Z\",\n    \"dateTo\": \"2026-10-06T21:00:00.000Z\",\n    \"report\": \"Updated report\",\n    \"type\": \"REPORT\",\n    \"mark\": \"N\",\n    \"approve\": \"N\"\n  }\n}\n```\n\n## Error response example\n\n422 — the new period overlaps another of the employee's reports:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"BITRIX_ERROR\",\n    \"message\": \"Period overlaps with another report\",\n    \"b24Code\": \"PERIOD_OVERLAP\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|----------|\n| 400 | `INVALID_PARAMS` | `id` is not a positive integer, the body has no field with a value, a field has the wrong type, a date has no time zone, or the body contains an unknown field such as `userId` or `files` |\n| 404 | `ENTITY_NOT_FOUND` | No report with this `id` exists |\n| 403 | `BITRIX_ACCESS_DENIED` | The report belongs to another employee, and the credential owner lacks Bitrix24 permissions to change that employee's reports |\n| 422 | `BITRIX_ERROR` | The new period overlaps another of the employee's reports; `b24Code` in the response is `PERIOD_OVERLAP` |\n| 422 | `BITRIX_ERROR` | Bitrix24 refused the operation for another reason |\n| 409 | `TIMEMAN_MODULE_NOT_ENABLED` | Time Management is not available on this portal |\n| 502 | `BITRIX_UNAVAILABLE` | Bitrix24 is unavailable or returned a response of an unexpected shape |\n| 401 | `MISSING_API_KEY` | The `X-Api-Key` header was not passed |\n| 401 | `TOKEN_MISSING` | An app key was sent without a session token in `Authorization: Bearer` |\n| 401 | `INVALID_SESSION` | The session token is invalid or has expired |\n| 403 | `WRITE_BLOCKED_READONLY_KEY` | The key is READONLY and cannot change reports |\n| 403 | `SCOPE_DENIED` | The key lacks the `timeman` scope |\n| 429 | `RATE_LIMITED` | The general request limit was exceeded |\n\nThe full list of common API errors — [Errors](\u002Fdocs\u002Ferrors).\n\n## Known specifics\n\n- **Employees can change their own reports.** Manager permissions are not required for that.\n- **A submitted report can be changed too.** It stays submitted, and `mark` and `approve` do not change.\n- **An overlapping period is not shifted.** When a report is created, the start of such a period moves to the day after the overlapping report; when a report is updated, the request is refused.\n- **Task and event keys in the response are uppercase.** In the `tasks` and `events` arrays of the response, `id` comes back as `ID`, `title` as `TITLE`, and the task `time` as `TIME`.\n\n## See also\n\n- [Create a work report](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Fcreate)\n- [Read a work report](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Fget)\n- [Send a work report](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Fsend)\n- [Submit a work report](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Fsubmit)\n- [Work reports](\u002Fdocs\u002Fworkday\u002Fwork-reports)\n- [Daily reports](\u002Fdocs\u002Fworkday\u002Fdaily-reports)\n- [Workday](\u002Fdocs\u002Fworkday)\n","## Send a work report\n\n`POST \u002Fv1\u002Fworkday\u002Fwork-reports\u002F:id\u002Fsend`\n\nSends a previously created work report by its ID and marks it as submitted without changing the text.\n\nRequires the `timeman` scope. Bitrix24 checks the credential owner’s permissions. READONLY keys can read reports and cannot write them.\n\n## Parameters\n\n| Parameter | Type | Required | Default | Description |\n|----------|-----|:-----:|-----------|----------|\n| `id` (path) | integer | yes | — | Report ID. List: [`GET \u002Fv1\u002Fworkday\u002Fwork-reports`](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Flist) |\n\nNo request body is needed. An empty object `{}` is accepted, and any field in the body returns `400 INVALID_PARAMS`.\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl -X POST \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fworkday\u002Fwork-reports\u002F159\u002Fsend\" \\\n  -H \"X-Api-Key: YOUR_API_KEY\"\n```\n\n### curl — OAuth application\n\n```bash\ncurl -X POST \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fworkday\u002Fwork-reports\u002F159\u002Fsend\" \\\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\u002Fworkday\u002Fwork-reports\u002F159\u002Fsend', {\n  method: 'POST',\n  headers: {\n    'X-Api-Key': 'YOUR_API_KEY',\n  },\n})\nconst { data } = await res.json()\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fworkday\u002Fwork-reports\u002F159\u002Fsend', {\n  method: 'POST',\n  headers: {\n    'X-Api-Key': 'YOUR_APP_KEY',\n    'Authorization': 'Bearer USER_SESSION_TOKEN',\n  },\n})\nconst { data } = await res.json()\n```\n\n## Response fields\n\n| Field | Type | Description |\n|------|-----|----------|\n| `success` | boolean | `true` when the report is sent |\n| `data` | object | The submitted report. All fields — [Report fields](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Ffields) |\n\n## Response example\n\nThe main report fields are shown. For the full list, see [Report fields](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Ffields):\n\n```json\n{\n  \"success\": true,\n  \"data\": {\n    \"id\": 159,\n    \"userId\": 101,\n    \"active\": true,\n    \"reportType\": \"day\",\n    \"reportDate\": \"2026-10-06T19:09:31.000Z\",\n    \"dateFrom\": \"2026-10-06T21:00:00.000Z\",\n    \"dateTo\": \"2026-10-06T21:00:00.000Z\",\n    \"report\": \"Weekly report\",\n    \"type\": \"REPORT\",\n    \"mark\": \"N\",\n    \"approve\": \"Y\"\n  }\n}\n```\n\n## Error response example\n\n404 — no report with this `id` exists:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"ENTITY_NOT_FOUND\",\n    \"message\": \"Report not found.\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|----------|\n| 400 | `INVALID_PARAMS` | `id` is not a positive integer, the request body is not a JSON object, or the body contains a field |\n| 404 | `ENTITY_NOT_FOUND` | No report with this `id` exists |\n| 403 | `BITRIX_ACCESS_DENIED` | The report belongs to another employee, and the credential owner lacks Bitrix24 permissions to change that employee's reports |\n| 409 | `TIMEMAN_MODULE_NOT_ENABLED` | Time Management is not available on this portal |\n| 422 | `BITRIX_ERROR` | Bitrix24 refused the operation |\n| 502 | `BITRIX_UNAVAILABLE` | Bitrix24 is unavailable or returned a response of an unexpected shape |\n| 401 | `MISSING_API_KEY` | The `X-Api-Key` header was not passed |\n| 401 | `TOKEN_MISSING` | An app key was sent without a session token in `Authorization: Bearer` |\n| 401 | `INVALID_SESSION` | The session token is invalid or has expired |\n| 403 | `WRITE_BLOCKED_READONLY_KEY` | The key is READONLY and cannot send reports |\n| 403 | `SCOPE_DENIED` | The key lacks the `timeman` scope |\n| 429 | `RATE_LIMITED` | The general request limit was exceeded |\n\nThe full list of common API errors — [Errors](\u002Fdocs\u002Ferrors).\n\n## Known specifics\n\n- **Confirmation depends on the employee's managers.** If the employee has managers, the report waits for their mark: `approve` is `\"N\"`. If the employee has no managers, the report is confirmed immediately: `approve` is `\"Y\"`.\n- **Sending again changes nothing.** A report that is already submitted is returned unchanged.\n\n## See also\n\n- [Create a work report](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Fcreate)\n- [Update a work report](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Fupdate)\n- [Submit a work report](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Fsubmit)\n- [Approve a work report](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Fapprove)\n- [Work reports](\u002Fdocs\u002Fworkday\u002Fwork-reports)\n- [Daily reports](\u002Fdocs\u002Fworkday\u002Fdaily-reports)\n- [Workday](\u002Fdocs\u002Fworkday)\n","## Submit a work report\n\n`POST \u002Fv1\u002Fworkday\u002Fwork-reports\u002Fsubmit`\n\nSubmits an existing work report, or creates a new one and submits it immediately.\n\nRequires the `timeman` scope. Bitrix24 checks the credential owner’s permissions. READONLY keys can read reports and cannot write them.\n\n## Request fields (body)\n\n| Field | Type | Required | Description |\n|------|-----|:-----:|----------|\n| `reportText` | string | yes | Report text. With `reportId`, it replaces the report text, and an empty string clears it |\n| `reportId` | integer | no | Report ID. List: [`GET \u002Fv1\u002Fworkday\u002Fwork-reports`](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Flist). Without `reportId`, a new report is created and submitted for the credential owner |\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl -X POST https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fworkday\u002Fwork-reports\u002Fsubmit \\\n  -H \"X-Api-Key: YOUR_API_KEY\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{ \"reportId\": 143, \"reportText\": \"Weekly report\" }'\n```\n\n### curl — OAuth application\n\n```bash\ncurl -X POST https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fworkday\u002Fwork-reports\u002Fsubmit \\\n  -H \"X-Api-Key: YOUR_APP_KEY\" \\\n  -H \"Authorization: Bearer USER_SESSION_TOKEN\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{ \"reportId\": 143, \"reportText\": \"Weekly report\" }'\n```\n\n### JavaScript — personal key\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fworkday\u002Fwork-reports\u002Fsubmit', {\n  method: 'POST',\n  headers: {\n    'X-Api-Key': 'YOUR_API_KEY',\n    'Content-Type': 'application\u002Fjson',\n  },\n  body: JSON.stringify({\n    reportId: 143,\n    reportText: 'Weekly report',\n  }),\n})\nconst { data } = await res.json()\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fworkday\u002Fwork-reports\u002Fsubmit', {\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({\n    reportId: 143,\n    reportText: 'Weekly report',\n  }),\n})\nconst { data } = await res.json()\n```\n\n## Response fields\n\n| Field | Type | Description |\n|------|-----|----------|\n| `success` | boolean | `true` when the report is submitted |\n| `data` | object | The submitted report. All fields — [Report fields](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Ffields) |\n\n## Response example\n\nThe main report fields are shown. For the full list, see [Report fields](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Ffields):\n\n```json\n{\n  \"success\": true,\n  \"data\": {\n    \"id\": 143,\n    \"userId\": 101,\n    \"active\": true,\n    \"reportType\": \"day\",\n    \"reportDate\": \"2026-10-06T18:22:40.000Z\",\n    \"dateFrom\": \"2026-10-05T21:00:00.000Z\",\n    \"dateTo\": \"2026-10-05T21:00:00.000Z\",\n    \"report\": \"Weekly report\",\n    \"type\": \"REPORT\",\n    \"mark\": \"N\",\n    \"approve\": \"Y\"\n  }\n}\n```\n\n## Error response example\n\n400 — `reportText` is missing:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"INVALID_PARAMS\",\n    \"message\": \"reportText is required and must be a string\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|----------|\n| 400 | `INVALID_PARAMS` | `reportText` is missing, `reportId` is not a positive integer, or the body contains an unknown field |\n| 404 | `ENTITY_NOT_FOUND` | No report with this `reportId` exists |\n| 403 | `BITRIX_ACCESS_DENIED` | The report belongs to another employee, and the credential owner lacks Bitrix24 permissions to change that employee's reports |\n| 409 | `TIMEMAN_MODULE_NOT_ENABLED` | Time Management is not available on this portal |\n| 422 | `BITRIX_ERROR` | Bitrix24 refused the operation |\n| 502 | `BITRIX_UNAVAILABLE` | Bitrix24 is unavailable or returned a response of an unexpected shape |\n| 401 | `MISSING_API_KEY` | The `X-Api-Key` header was not passed |\n| 401 | `TOKEN_MISSING` | An app key was sent without a session token in `Authorization: Bearer` |\n| 401 | `INVALID_SESSION` | The session token is invalid or has expired |\n| 403 | `WRITE_BLOCKED_READONLY_KEY` | The key is READONLY and cannot submit reports |\n| 403 | `SCOPE_DENIED` | The key lacks the `timeman` scope |\n| 429 | `RATE_LIMITED` | The general request limit was exceeded |\n\nThe full list of common API errors — [Errors](\u002Fdocs\u002Ferrors).\n\n## Known specifics\n\n- **A new report's period is chosen as when creating a report.** Without `reportId`, the period is chosen the same way as when a report is created without `dateFrom` and `dateTo`: [Create a work report](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Fcreate).\n- **Confirmation depends on the employee's managers.** If the employee has managers, the submitted report waits for their mark: `approve` is `\"N\"`. If the employee has no managers, the report is confirmed immediately: `approve` is `\"Y\"`.\n- **A submitted report can be submitted again.** The text is replaced, the report stays submitted, and `mark` and `approve` do not change.\n\n## See also\n\n- [Send a work report](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Fsend)\n- [Create a work report](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Fcreate)\n- [List work reports](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Flist)\n- [Work reports](\u002Fdocs\u002Fworkday\u002Fwork-reports)\n- [Daily reports](\u002Fdocs\u002Fworkday\u002Fdaily-reports)\n- [Workday](\u002Fdocs\u002Fworkday)\n","## Approve a work report\n\n`POST \u002Fv1\u002Fworkday\u002Fwork-reports\u002F:id\u002Fapprove`\n\nGives an employee's work report a positive mark and confirms the report.\n\nRequires the `timeman` scope. Bitrix24 checks the credential owner’s permissions. READONLY keys can read reports and cannot write them.\n\n## Parameters\n\n| Parameter | Type | Required | Default | Description |\n|----------|-----|:-----:|-----------|----------|\n| `id` (path) | integer | yes | — | Report ID. List: [`GET \u002Fv1\u002Fworkday\u002Fwork-reports`](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Flist) |\n\nNo request body is needed. An empty object `{}` is accepted, and any field in the body returns `400 INVALID_PARAMS`.\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl -X POST \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fworkday\u002Fwork-reports\u002F167\u002Fapprove\" \\\n  -H \"X-Api-Key: YOUR_API_KEY\"\n```\n\n### curl — OAuth application\n\n```bash\ncurl -X POST \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fworkday\u002Fwork-reports\u002F167\u002Fapprove\" \\\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\u002Fworkday\u002Fwork-reports\u002F167\u002Fapprove', {\n  method: 'POST',\n  headers: {\n    'X-Api-Key': 'YOUR_API_KEY',\n  },\n})\nconst { data } = await res.json()\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fworkday\u002Fwork-reports\u002F167\u002Fapprove', {\n  method: 'POST',\n  headers: {\n    'X-Api-Key': 'YOUR_APP_KEY',\n    'Authorization': 'Bearer USER_SESSION_TOKEN',\n  },\n})\nconst { data } = await res.json()\n```\n\n## Response fields\n\n| Field | Type | Description |\n|------|-----|----------|\n| `success` | boolean | `true` when the request succeeds |\n| `data` | boolean | `true` — the mark is set |\n\n## Response example\n\n```json\n{\n  \"success\": true,\n  \"data\": true\n}\n```\n\n## Error response example\n\n422 — no report with this `id` exists:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"BITRIX_ERROR\",\n    \"message\": \"Report not found or cannot be changed\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|----------|\n| 400 | `INVALID_PARAMS` | `id` is not a positive integer, the request body is not a JSON object, or the body contains a field |\n| 422 | `BITRIX_ERROR` | No report with this `id` exists, the credential owner lacks Bitrix24 permission to mark this employee's reports, or Bitrix24 refused the operation |\n| 409 | `TIMEMAN_MODULE_NOT_ENABLED` | Time Management is not available on this portal |\n| 502 | `BITRIX_UNAVAILABLE` | Bitrix24 is unavailable |\n| 401 | `MISSING_API_KEY` | The `X-Api-Key` header was not passed |\n| 401 | `TOKEN_MISSING` | An app key was sent without a session token in `Authorization: Bearer` |\n| 401 | `INVALID_SESSION` | The session token is invalid or has expired |\n| 403 | `WRITE_BLOCKED_READONLY_KEY` | The key is READONLY and cannot approve reports |\n| 403 | `SCOPE_DENIED` | The key lacks the `timeman` scope |\n| 429 | `RATE_LIMITED` | The general request limit was exceeded |\n\nThe full list of common API errors — [Errors](\u002Fdocs\u002Ferrors).\n\n## Known specifics\n\n- **What changes in the report.** `mark` becomes `\"G\"` and `approve` becomes `\"Y\"`. `approve` is the report confirmation: it is `\"Y\"` for both positive and negative marks, and `mark` holds the mark itself. The changes are visible in [`GET \u002Fv1\u002Fworkday\u002Fwork-reports\u002F:id`](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Fget).\n- **Marking your own report also requires permission.** An employee without permission to mark reports gets `422 BITRIX_ERROR` for their own report too.\n- **A report that has not been submitted can be approved too.** It stays unsubmitted, and a submitted report stays submitted: `active` does not change.\n- **Calling again does not return an error.** The mark stays positive, and the response is `true` again.\n\n## See also\n\n- [Send a work report](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Fsend)\n- [Read a work report](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Fget)\n- [Reject a work report](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Freject)\n- [Disapprove a work report](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Fdisapprove)\n- [Work reports](\u002Fdocs\u002Fworkday\u002Fwork-reports)\n- [Daily reports](\u002Fdocs\u002Fworkday\u002Fdaily-reports)\n- [Workday](\u002Fdocs\u002Fworkday)\n","## Reject a work report\n\n`POST \u002Fv1\u002Fworkday\u002Fwork-reports\u002F:id\u002Freject`\n\nGives an employee's work report a neutral mark and removes the report confirmation.\n\nRequires the `timeman` scope. Bitrix24 checks the credential owner’s permissions. READONLY keys can read reports and cannot write them.\n\n## Parameters\n\n| Parameter | Type | Required | Default | Description |\n|----------|-----|:-----:|-----------|----------|\n| `id` (path) | integer | yes | — | Report ID. List: [`GET \u002Fv1\u002Fworkday\u002Fwork-reports`](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Flist) |\n\nNo request body is needed. An empty object `{}` is accepted, and any field in the body returns `400 INVALID_PARAMS`.\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl -X POST \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fworkday\u002Fwork-reports\u002F167\u002Freject\" \\\n  -H \"X-Api-Key: YOUR_API_KEY\"\n```\n\n### curl — OAuth application\n\n```bash\ncurl -X POST \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fworkday\u002Fwork-reports\u002F167\u002Freject\" \\\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\u002Fworkday\u002Fwork-reports\u002F167\u002Freject', {\n  method: 'POST',\n  headers: {\n    'X-Api-Key': 'YOUR_API_KEY',\n  },\n})\nconst { data } = await res.json()\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fworkday\u002Fwork-reports\u002F167\u002Freject', {\n  method: 'POST',\n  headers: {\n    'X-Api-Key': 'YOUR_APP_KEY',\n    'Authorization': 'Bearer USER_SESSION_TOKEN',\n  },\n})\nconst { data } = await res.json()\n```\n\n## Response fields\n\n| Field | Type | Description |\n|------|-----|----------|\n| `success` | boolean | `true` when the request succeeds |\n| `data` | boolean | `true` — the mark is set |\n\n## Response example\n\n```json\n{\n  \"success\": true,\n  \"data\": true\n}\n```\n\n## Error response example\n\n422 — no report with this `id` exists:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"BITRIX_ERROR\",\n    \"message\": \"Report not found or cannot be changed\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|----------|\n| 400 | `INVALID_PARAMS` | `id` is not a positive integer, the request body is not a JSON object, or the body contains a field |\n| 422 | `BITRIX_ERROR` | No report with this `id` exists, the credential owner lacks Bitrix24 permission to mark this employee's reports, or Bitrix24 refused the operation |\n| 409 | `TIMEMAN_MODULE_NOT_ENABLED` | Time Management is not available on this portal |\n| 502 | `BITRIX_UNAVAILABLE` | Bitrix24 is unavailable |\n| 401 | `MISSING_API_KEY` | The `X-Api-Key` header was not passed |\n| 401 | `TOKEN_MISSING` | An app key was sent without a session token in `Authorization: Bearer` |\n| 401 | `INVALID_SESSION` | The session token is invalid or has expired |\n| 403 | `WRITE_BLOCKED_READONLY_KEY` | The key is READONLY and cannot mark reports |\n| 403 | `SCOPE_DENIED` | The key lacks the `timeman` scope |\n| 429 | `RATE_LIMITED` | The general request limit was exceeded |\n\nThe full list of common API errors — [Errors](\u002Fdocs\u002Ferrors).\n\n## Known specifics\n\n- **What changes in the report.** `mark` becomes `\"N\"` and `approve` becomes `\"N\"`: the report confirmation is removed. The changes are visible in [`GET \u002Fv1\u002Fworkday\u002Fwork-reports\u002F:id`](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Fget).\n- **Marking your own report also requires permission.** An employee without permission to mark reports gets `422 BITRIX_ERROR` for their own report too.\n- **A report that has not been submitted can be marked too.** It stays unsubmitted, and a submitted report stays submitted: `active` does not change.\n- **Calling again does not return an error.** The mark stays neutral, and the response is `true` again.\n\n## See also\n\n- [Approve a work report](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Fapprove)\n- [Disapprove a work report](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Fdisapprove)\n- [Read a work report](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Fget)\n- [Send a work report](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Fsend)\n- [Work reports](\u002Fdocs\u002Fworkday\u002Fwork-reports)\n- [Daily reports](\u002Fdocs\u002Fworkday\u002Fdaily-reports)\n- [Workday](\u002Fdocs\u002Fworkday)\n","## Disapprove a work report\n\n`POST \u002Fv1\u002Fworkday\u002Fwork-reports\u002F:id\u002Fdisapprove`\n\nGives an employee's work report a negative mark in place of a positive or neutral one.\n\nRequires the `timeman` scope. Bitrix24 checks the credential owner’s permissions. READONLY keys can read reports and cannot write them.\n\n## Parameters\n\n| Parameter | Type | Required | Default | Description |\n|----------|-----|:-----:|-----------|----------|\n| `id` (path) | integer | yes | — | Report ID. List: [`GET \u002Fv1\u002Fworkday\u002Fwork-reports`](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Flist) |\n\nNo request body is needed. An empty object `{}` is accepted, and any field in the body returns `400 INVALID_PARAMS`.\n\n## Examples\n\n### curl — personal key\n\n```bash\ncurl -X POST \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fworkday\u002Fwork-reports\u002F167\u002Fdisapprove\" \\\n  -H \"X-Api-Key: YOUR_API_KEY\"\n```\n\n### curl — OAuth application\n\n```bash\ncurl -X POST \"https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fworkday\u002Fwork-reports\u002F167\u002Fdisapprove\" \\\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\u002Fworkday\u002Fwork-reports\u002F167\u002Fdisapprove', {\n  method: 'POST',\n  headers: {\n    'X-Api-Key': 'YOUR_API_KEY',\n  },\n})\nconst { data } = await res.json()\n```\n\n### JavaScript — OAuth application\n\n```javascript\nconst res = await fetch('https:\u002F\u002Fvibecode.bitrix24.com\u002Fv1\u002Fworkday\u002Fwork-reports\u002F167\u002Fdisapprove', {\n  method: 'POST',\n  headers: {\n    'X-Api-Key': 'YOUR_APP_KEY',\n    'Authorization': 'Bearer USER_SESSION_TOKEN',\n  },\n})\nconst { data } = await res.json()\n```\n\n## Response fields\n\n| Field | Type | Description |\n|------|-----|----------|\n| `success` | boolean | `true` when the request succeeds |\n| `data` | boolean | `true` — the mark is set |\n\n## Response example\n\n```json\n{\n  \"success\": true,\n  \"data\": true\n}\n```\n\n## Error response example\n\n422 — no report with this `id` exists:\n\n```json\n{\n  \"success\": false,\n  \"error\": {\n    \"code\": \"BITRIX_ERROR\",\n    \"message\": \"Report not found or cannot be changed\"\n  }\n}\n```\n\n## Errors\n\n| HTTP | Code | Description |\n|------|-----|----------|\n| 400 | `INVALID_PARAMS` | `id` is not a positive integer, the request body is not a JSON object, or the body contains a field |\n| 422 | `BITRIX_ERROR` | No report with this `id` exists, the credential owner lacks Bitrix24 permission to mark this employee's reports, or Bitrix24 refused the operation |\n| 409 | `TIMEMAN_MODULE_NOT_ENABLED` | Time Management is not available on this portal |\n| 502 | `BITRIX_UNAVAILABLE` | Bitrix24 is unavailable |\n| 401 | `MISSING_API_KEY` | The `X-Api-Key` header was not passed |\n| 401 | `TOKEN_MISSING` | An app key was sent without a session token in `Authorization: Bearer` |\n| 401 | `INVALID_SESSION` | The session token is invalid or has expired |\n| 403 | `WRITE_BLOCKED_READONLY_KEY` | The key is READONLY and cannot mark reports |\n| 403 | `SCOPE_DENIED` | The key lacks the `timeman` scope |\n| 429 | `RATE_LIMITED` | The general request limit was exceeded |\n\nThe full list of common API errors — [Errors](\u002Fdocs\u002Ferrors).\n\n## Known specifics\n\n- **What changes in the report.** `mark` becomes `\"B\"` and `approve` becomes `\"Y\"`. `approve` is the report confirmation: it is `\"Y\"` for both positive and negative marks, and `mark` holds the mark itself. The changes are visible in [`GET \u002Fv1\u002Fworkday\u002Fwork-reports\u002F:id`](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Fget).\n- **Marking your own report also requires permission.** An employee without permission to mark reports gets `422 BITRIX_ERROR` for their own report too.\n- **A report that has not been submitted can be marked too.** It stays unsubmitted, and a submitted report stays submitted: `active` does not change.\n- **Calling again does not return an error.** The mark stays negative, and the response is `true` again.\n\n## See also\n\n- [Approve a work report](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Fapprove)\n- [Reject a work report](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Freject)\n- [Read a work report](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Fget)\n- [Send a work report](\u002Fdocs\u002Fworkday\u002Fwork-reports\u002Fsend)\n- [Work reports](\u002Fdocs\u002Fworkday\u002Fwork-reports)\n- [Daily reports](\u002Fdocs\u002Fworkday\u002Fdaily-reports)\n- [Workday](\u002Fdocs\u002Fworkday)\n",1795000593524]