Most of your hiring data lives inside your ATS, and getting it anywhere else usually means one of two bad options. You export a CSV by hand, or you write a script that polls the 100Hires API every few minutes and still reacts late.

Webhooks remove the wait. Register an HTTPS endpoint once and 100Hires posts to it the instant something happens, so your CRM, warehouse, or team chat updates on its own.

This page covers the events you can subscribe to, how to register a webhook, the no-code path, and the limits worth knowing first.

Trigger workflows the instant something changes

A polling loop is wasted work. It hits the API on a schedule whether or not anything changed, makes unnecessary requests, and still lags behind real time by however long the interval is. Webhooks invert that. Nothing fires until an actual event happens.

Set up with an API key, not a settings toggle

There is no webhook toggle to flip. Webhooks are part of the 100Hires Developer API, so setup starts with an API key from Settings, Integrations, and the registration itself is one API call. If you would rather not write code at all, skip to the Zapier path below.

Register a webhook with one API call

Point a webhook at the whole company or at a single job. Company scope catches events across every role, and job scope keeps a focused stream for a single job.

Company-level subscription:

POST https://api.100hires.com/v2/companies/{id}/webhooks
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

{"url": "https://your-app.example.com/hooks/100hires"}

Job-level subscription:

POST https://api.100hires.com/v2/jobs/{id}/webhooks
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

{"url": "https://your-app.example.com/hooks/100hires"}

List your webhooks with a GET on the same path, and remove one with a DELETE. The request body accepts only a url field, and it must be HTTPS and 2048 characters or fewer. The full event catalog and payload schema live in the 100Hires API docs at https://api.100hires.com/v2/openapi.json.

Webhooks are one slice of the 100Hires Developer API. If you would rather drive the whole pipeline in plain English, the same account connects to AI assistants through the 100Hires MCP server.

Prefer no code? Route the same events through Zapier

The 100Hires API also backs a native Zapier integration, so you can connect events to thousands of downstream apps without hosting an endpoint. Make and n8n can connect to the same API.

The raw webhook is a plain HTTPS POST with no signing secret or built-in retries, so when you want managed, retried delivery, the native Zapier path handles it for you.

How 100Hires webhooks compare to a typical ATS

Good to know before you wire it up

Two honest limits. First, there is no UI to add a webhook, so you register through the API or the 100Hires MCP server, not a settings screen.

Second, the webhook is a plain HTTPS POST, with no signing secret and no documented retries. If you need authenticated or guaranteed delivery, route events through the native Zapier or Make integration, or validate requests on your own endpoint with a secret URL path.

For the exact event names and payload fields, the 100Hires API docs at https://api.100hires.com/v2/openapi.json are the source of truth.