Use 100Hires Webhooks for Custom Integrations

Webhooks let your systems react to hiring events in 100Hires the moment they happen, without polling our API on a schedule.

What webhooks are

A webhook is a small HTTP listener you stand up on your side. 100Hires calls that endpoint over HTTPS every time a subscribed event fires. Compared to polling the API every few minutes, webhooks are instant, lighter on rate limits, and easier to scale across many jobs.

Supported events

You can subscribe to any of these events:

• New application submitted
• Application stage change
• Candidate hired
• Candidate disqualified
• Interview scheduled
• AI Score generated
• Candidate created
• Candidate updated

Company-level vs per-job webhooks

100Hires supports two scopes:

• Company-level webhooks fire for every matching event across every job in your account. Use them for cross-cutting integrations - CRM sync, BI dashboards, or a Slack firehose.
• Per-job webhooks fire only for events on one specific job. Use them for one-off integrations tied to a high-priority role.

Setting up via API

Webhooks are registered through the Developer API, not through the UI. Send a POST to /v2/webhooks for a company-level subscription, or to /v2/jobs/{job_id}/webhooks for a per-job one. Include your endpoint URL and the list of event types you want. See the Developer API v2 Overview for auth headers and rate limits.

Payload structure

Each delivery is a JSON body with the event type, the affected entity (candidate, application, interview, etc.), and metadata such as timestamp and the user who triggered it. Full per-event schemas live in the 100Hires OpenAPI spec.

Retry logic

If your endpoint returns a non-2xx response or times out, 100Hires retries with exponential backoff: 1 minute, 5 minutes, 30 minutes, 2 hours, 12 hours. After roughly five failed attempts the event is dropped from the queue. Because the same event can be delivered more than once, build your handler to be idempotent - deduplicate on the event ID and process duplicates safely.

Security

Every request includes a signature header derived from your webhook secret. Verify the signature on your side before processing the payload so spoofed requests can't reach your business logic. If you also need IP-level filtering, contact 100Hires support for the current outbound IP range and add an allowlist on your firewall.

Common use cases

• Sync new hires from 100Hires into BambooHR, Rippling, or Gusto.
• Push applications above an AI Score threshold to a Slack channel.
• Populate a custom executive dashboard with live pipeline counts.
• Mirror stage changes to a CRM like Salesforce or HubSpot.

Testing

Before pointing webhooks at production, send them to a free inspector tool such as Beeceptor or webhook.site. You'll see the live payload shape, headers, and signature in your browser, which makes it much faster to build and debug your handler.

Updated on: 15/06/2026