HIhibob
Background check webhooks

Background check cancelled

Fired when a recruiter cancels an in-flight or pending background check in Bob. Partners stop processing at the provider and do not call PATCH for a terminal status unless product guidance says otherwise.

Delivery is at-least-once — partners handle duplicates idempotently using data.backgroundCheckRequestId. The cancelled payload does not include packageId.

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>.

postWebhookbackgroundCheckCancelled

Headers

bob-signaturestring required

Base64-encoded signature sent with each webhook request. Use it to verify that the request came from Bob.

Payload

versionstring required

Webhook payload schema version. Currently always "v2".

type'backgroundCheck.cancelled' required
triggeredBystring required

Backend ID of the employee who triggered the event, or system.

triggeredAtstring required

When the event occurred, as an ISO 8601 timestamp with Z suffix (for example "2026-05-28T11:00:00Z").

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.