Background check triggered
Fired when a recruiter orders a background check for a candidate with a selected partner package. Delivery is at-least-once — partners handle duplicates idempotently using data.backgroundCheckRequestId.
After receiving this event, partners fetch <a href="https://apidocs.hibob.com/reference/get_hiring-background-checks-backgroundcheckrequestid">Get background check details</a> and then start processing at the provider.
Every webhook request carries a bob-signature header that partners verify before processing. See HiBob's <a href="https://apidocs.hibob.com/reference/getting-started-webhooks#how-does-bob-calculate-the-signature">webhook signature verification guide</a>.
Headers
Base64-encoded signature sent with each webhook request. Use it to verify that the request came from Bob.
Payload
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.