HIhibob
Workforce Planning Webhooks

Position opening created webhook

Webhook sent when a new position opening is created. Position openings are always linked to a Position in Bob.

They allow organizations to plan multiple hiring scenarios under the same position (e.g. maternity leave replacements or organizational growth) without duplicating positions. Each opening can have its recruitment status, expected start date, and opening name.

Best practice: Use the event as a notification only, and retrieve the complete position opening details using the <a href="https://apidocs.hibob.com/reference/post_positions-position-openings-search" target="_blank">Read company positions openings</a> API endpoint. Note that position opening events don't include the position ID; you can get it by retrieving the opening details.

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

postWebhookpositionOpeningCreated

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'workforcePlanning.positionOpening.created' required

The event type for position opening creation

triggeredBystring required

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

triggeredAtstring date-time required

The timestamp when the event occurred

versionstring required

The webhook version

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.