لوكلاء AI: ملف markdown لهذه الصفحة — /docs-content-en/workday/schedules-users-delete.md فهرس التوثيق — /llms.txt
مقالات التوثيق متاحة حاليًا باللغة الإنجليزية فقط.
Remove an employee from a schedule
DELETE /v1/workday/schedules/:id/users/:userId
Excludes an employee from a work schedule, including a schedule assigned to all employees, and removes their future shifts on this schedule. To bring the employee back to the schedule, add them again.
Requires the timeman scope and permission to manage work schedules in Bitrix24: the Bitrix24 account administrator always has it; an employee is granted it in the Time Management access permission settings. READONLY keys cannot exclude an employee from a schedule. To add an employee to a schedule, see Add an employee to a schedule.
Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
Parameterid (path) |
Typeinteger | Requiredyes | Default— | DescriptionWork schedule ID, a positive integer. Where to get it: the work schedules page of the Bitrix24 account (/timeman/schedules/); the API has no schedule list. Check by ID: GET /v1/workday/schedule |
ParameteruserId (path) |
Typeinteger | Requiredyes | Default— | DescriptionEmployee ID, a positive integer. List: GET /v1/users |
Examples
curl — personal key
curl -X DELETE "https://vibecode.bitrix24.com/v1/workday/schedules/13/users/503" \
-H "X-Api-Key: YOUR_API_KEY"
curl — OAuth application
curl -X DELETE "https://vibecode.bitrix24.com/v1/workday/schedules/13/users/503" \
-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/schedules/13/users/503', {
method: 'DELETE',
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/schedules/13/users/503', {
method: 'DELETE',
headers: {
'X-Api-Key': 'YOUR_APP_KEY',
'Authorization': 'Bearer USER_SESSION_TOKEN',
},
})
const { data } = await res.json()
Response fields
| Field | Type | Description |
|---|---|---|
Fieldsuccess |
Typeboolean | Descriptiontrue when the employee is excluded from the schedule |
Fielddata.schedule |
Typeobject | DescriptionThe schedule the employee was excluded from |
Fielddata.schedule.id |
Typeinteger | DescriptionSchedule ID |
Fielddata.schedule.name |
Typestring | DescriptionSchedule name |
Response example
{
"success": true,
"data": {
"schedule": {
"id": 13,
"name": "Office 5/2"
}
}
}
Error response example
404 — no schedule with this id, or it has been deleted:
{
"success": false,
"error": {
"code": "ENTITY_NOT_FOUND",
"message": "Schedule was not found"
}
}
Errors
| HTTP | Code | Description |
|---|---|---|
| HTTP400 | CodeINVALID_PARAMS |
Descriptionid or userId is not a positive integer |
| HTTP404 | CodeENTITY_NOT_FOUND |
DescriptionNo schedule with this id, including after deletion |
| HTTP422 | CodeBITRIX_ERROR |
DescriptionThe credential owner lacks permission to manage work schedules — the Bitrix24 text is in message |
| HTTP403 | CodeWRITE_BLOCKED_READONLY_KEY |
DescriptionThe key is in read-only mode |
| HTTP409 | CodeTIMEMAN_MODULE_NOT_ENABLED |
DescriptionTime Management is not available on this portal: the Time Management tool is switched off in the portal settings, or the module is not included in the plan |
| HTTP502 | CodeBITRIX_UNAVAILABLE |
DescriptionBitrix24 is unavailable or returned a response of an unexpected shape |
| HTTP401 | CodeMISSING_API_KEY |
DescriptionThe X-Api-Key header was not passed |
| HTTP401 | CodeTOKEN_MISSING |
DescriptionAn app key was sent without a session token in Authorization: Bearer |
| HTTP401 | CodeINVALID_SESSION |
DescriptionThe session token is invalid or has expired |
| HTTP403 | CodeSCOPE_DENIED |
DescriptionThe key lacks the timeman scope |
| HTTP429 | CodeRATE_LIMITED |
DescriptionThe general request limit was exceeded; the retry delay is in the Retry-After header |
The full list of common API errors — Errors.
Known specifics
Exclusion does not delete the schedule assignment. The employee remains among the assigned employees but is marked as excluded, so the schedule does not apply to them. POST /v1/workday/schedules/:id/users removes the mark.
The employee's other schedules stay unchanged. The exclusion applies only to the schedule identified by id.