HIhibob
Workforce Planning Webhooks

Position created webhook

Webhook sent when a new position is created in the Workforce Planning module.

Positions are a core entity of the Workforce Planning module, enabling you to allocate budgets and assign specific roles to positions for your workforce's current and future needs.

Best practice: Use the event as a notification only, and retrieve the complete position details using the <a href="https://apidocs.hibob.com/reference/post_objects-position-search" target="_blank">Read company positions</a> API endpoint.

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

postWebhookpositionCreated

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

The event type for position 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.