Create time off request in Hibob (Legacy)
HRIS API · write, waits for approval · 100% field coverage
Your agent can create time off request in Hibob (Legacy) through Apideck's HRIS API, the same call it makes for every HRIS app. It changes data in the customer's Hibob (Legacy) account, so it stops with the exact request until a person approves it. Apideck adds the customer's Hibob (Legacy) credentials, so no token ever reaches the agent.
The call
POST https://unify.apideck.com/hris/time-off-requests
Headers: x-apideck-service-id: hibob, plus your app id and the customer's consumer id. Apideck MCP tool: hris-time-off-requests-add. Agent operation id: unified.hris.timeOffRequestsAdd.
Body fields
| Field | Type | Description |
|---|---|---|
| employee_id | string | ID of the employee |
| policy_id | string | ID of the policy |
| status | string | The status of the time off request. |
| description | string | Description of the time off request. |
| start_date | string | The start date of the time off request. |
| end_date | string | The end date of the time off request. |
| request_date | string | The date the request was made. |
| request_type | string | The type of request |
| approval_date | string | The date the request was approved |
| units | string | The unit of time off requested. Possible values include: `hours`, `days`, or `other`. |
| amount | number | The amount of time off requested. |
| day_part | string | The day part of the time off request. |
| notes | object | |
| policy_type | string | The policy type of the time off request |
More for time off requests in Hibob (Legacy)
list_time_off_requestsget_time_off_requestdelete_time_off_request
Create time off request in other HRIS apps
The same call works for each of these; only the service id changes.