For AI agents: markdown of this page — /docs-content-en/workday/work-reports/reject.md documentation index — /llms.txt
Reject a work report
POST /v1/workday/work-reports/:id/reject
Gives an employee's work report a neutral mark and removes the report confirmation.
Requires the timeman scope. Bitrix24 checks the credential owner’s permissions. READONLY keys can read reports and cannot write them.
Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
id (path) |
integer | yes | — | Report ID. List: GET /v1/workday/work-reports |
No request body is needed. An empty object {} is accepted, and any field in the body returns 400 INVALID_PARAMS.
Examples
curl — personal key
curl -X POST "https://vibecode.bitrix24.com/v1/workday/work-reports/167/reject" \
-H "X-Api-Key: YOUR_API_KEY"
curl — OAuth application
curl -X POST "https://vibecode.bitrix24.com/v1/workday/work-reports/167/reject" \
-H "X-Api-Key: YOUR_APP_KEY" \
-H "Authorization: Bearer USER_SESSION_TOKEN"
JavaScript — personal key
const res = await fetch('https://vibecode.bitrix24.com/v1/workday/work-reports/167/reject', {
method: 'POST',
headers: {
'X-Api-Key': 'YOUR_API_KEY',
},
})
const { data } = await res.json()
JavaScript — OAuth application
const res = await fetch('https://vibecode.bitrix24.com/v1/workday/work-reports/167/reject', {
method: 'POST',
headers: {
'X-Api-Key': 'YOUR_APP_KEY',
'Authorization': 'Bearer USER_SESSION_TOKEN',
},
})
const { data } = await res.json()
Response fields
| Field | Type | Description |
|---|---|---|
success |
boolean | true when the request succeeds |
data |
boolean | true — the mark is set |
Response example
{
"success": true,
"data": true
}
Error response example
422 — no report with this id exists:
{
"success": false,
"error": {
"code": "BITRIX_ERROR",
"message": "Report not found or cannot be changed"
}
}
Errors
| HTTP | Code | Description |
|---|---|---|
| 400 | INVALID_PARAMS |
id is not a positive integer, the request body is not a JSON object, or the body contains a field |
| 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 |
| 409 | TIMEMAN_MODULE_NOT_ENABLED |
Time Management is not available on this portal |
| 502 | BITRIX_UNAVAILABLE |
Bitrix24 is unavailable |
| 401 | MISSING_API_KEY |
The X-Api-Key header was not passed |
| 401 | TOKEN_MISSING |
An app key was sent without a session token in Authorization: Bearer |
| 401 | INVALID_SESSION |
The session token is invalid or has expired |
| 403 | WRITE_BLOCKED_READONLY_KEY |
The key is READONLY and cannot mark reports |
| 403 | SCOPE_DENIED |
The key lacks the timeman scope |
| 429 | RATE_LIMITED |
The general request limit was exceeded |
The full list of common API errors — Errors.
Known specifics
- What changes in the report.
markbecomes"N"andapprovebecomes"N": the report confirmation is removed. The changes are visible inGET /v1/workday/work-reports/:id. - Marking your own report also requires permission. An employee without permission to mark reports gets
422 BITRIX_ERRORfor their own report too. - A report that has not been submitted can be marked too. It stays unsubmitted, and a submitted report stays submitted:
activedoes not change. - Calling again does not return an error. The mark stays neutral, and the response is
trueagain.