HIhibob
Workforce Planning Webhooks

Position budget updated webhook

Webhook sent when position budget fields are modified. Position budgets are always linked to a Position in Bob.

They allow tracking of the financial allocation for specific roles within the organization. The payload includes fieldUpdatesIds to indicate which fields were changed.

Best practice: Use the event as a notification only, and retrieve the complete position budget details using the <a href="https://apidocs.hibob.com/reference/post_positions-position-budget-search" target="_blank">Read company positions budgets</a> API endpoint. Use the fieldUpdatesIds from the payload to retrieve only the updated field values. Note that budget events include the position ID, because budget details don't return it.

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

postWebhookpositionBudgetUpdated

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.positionBudget.updated' required

The event type for position budget update

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.