HIhibob
Time off Webhooks

Time off request approved

Triggered when approving a time off request.

For auto-approved requests, two events are sent in sequence: requested then approved.

In the right panel, open Examples and select Payload Example to see a real payload.

postWebhooktimeoffRequestApproved

Headers

bob-signaturestring required
Example:EQScIBkAtTKFW0ictgt5zzOsqIc2+xGEsM88jOdLuW4CM/a3gLEfrKV+IC5IHx0xbirzLKPIfaZjCGwzuiyI8w==

Base64-encoded signature sent with each webhook request. Use it to verify that the request came from Bob. To verify webhook authenticity, see <a href="https://apidocs.hibob.com/update/reference?isFramePreview=true#how-does-bob-calculate-the-signature" target="_blank">How does Bob calculate the signature</a>.

Payload

companyIdnumber required

The company ID

type'timeoff.request.approved' required

Event type for time off request approved

triggeredBystring required

The backend-id of the employee that triggered the event, or 'system' for system-triggered events

triggeredAtstring required

The timestamp when the event occurred (ISO 8601-style string)

versionstring required

The webhook version (e.g., v2)

Response

Webhook received successfully

Changes

Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.