HIhibob
Employee data Webhooks

Employee terminated

Triggered when an employee is set as terminated or on Garden leave (whichever occurs first), once the corresponding lifecycle entry becomes effective.

Lifecycle events are triggered automatically at midnight on the effective date of the lifecycle table entry (according to the site's timezone).

To revoke access to Bob when Revoke access immediately is selected on a termination request, subscribe to <a href="https://apidocs.hibob.com/reference/post_webhook_employee-access-revoked-immediately" target="_blank">employee.access.revoked.immediately</a>.

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

postWebhookemployeeLeft

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/reference/getting-started-webhooks#how-does-bob-calculate-the-signature" target="_blank">How does Bob calculate the signature</a>.

Payload

companyIdnumber required

The company ID

type'employee.left' required

Event type for employee terminated or on Garden leave

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.