Per gli agenti AI: markdown di questa pagina — /docs-content-en/workday/time-control-explain.md indice della documentazione — /llms.txt
Gli articoli della documentazione sono attualmente disponibili solo in inglese.
Explain an absence
POST /v1/workday/time-control/reports/:absenceId calls timeman.timecontrol.report.add.
Required: positive absenceId, nonempty text, and the absence month (1-12) and year (1900-3000). type: WORK or PRIVATE (defaults to PRIVATE). calendar: boolean, defaults to true and creates a calendar event. userId is honored only for a Bitrix24 administrator; other callers write as the webhook owner or OAuth session user.
Before writing, Vibe reads report settings and the selected month's report and matches the absence ID and user. If it is invisible in that month or belongs to another user, the response is 404 ENTITY_NOT_FOUND without a write. Bitrix24 hides absences in its simple report view: explaining an absence requires a visible full report. Empty text or missing month returns 400 before an upstream call. Success: { success: true, data: true }.
{"text":"Work meeting","month":10,"year":2026,"type":"WORK","calendar":false}Access and errors
Key scope: timeman. Bitrix24 enforces user permissions. 400 INVALID_PARAMS means invalid input; 403 means missing scope or Bitrix24 permissions; writes with a READONLY key return 403 WRITE_BLOCKED_READONLY_KEY; 409 TIMEMAN_MODULE_NOT_ENABLED means unavailable Time Management; 422 BITRIX_ERROR forwards a Bitrix24 business refusal with its text. Webhook credentials are scrubbed from responses.