ingested_after instead (see Choosing the right API). Webhooks send one event per request and are capped per day.
Quickstart
1
Get a URL that receives requests
Use your own endpoint, a catch-hook URL from Clay, Zapier, Make or n8n, or a free test URL from webhook.site. It must be
https and reachable on the public internet (not localhost or a private address).2
Check how many events your search makes
Free. Returns the average number of new matching jobs, and companies, per day over the last 7 days.
3
Create the webhook
search is the same body you send to Job Search, without page, limit, sort_by, sort_order, ingested_after or ingested_before. Unknown fields are rejected with a 422, so a typo can’t turn into an unfiltered webhook.id and its signing secret (whsec_...).4
Send a test event
Sends one signed
webhook.test event with a sample matching job right away, and tells you what your endpoint answered. Free.Events
Pick one or both with
events (default ["job.new"]). company.new is the one to use for “tell me when a company starts hiring for X”: one alert per company instead of one per opening.
Every request carries one event:
Verify the signature
Every request is signed with the Standard Webhooks scheme. The headers arewebhook-id (the event id, the same on every retry, so use it to ignore duplicates), webhook-timestamp and webhook-signature. Any Standard Webhooks library verifies them with your whsec_ secret.
GET /v2/webhooks/{id} shows the secret again. POST /v2/webhooks/{id}/rotate-secret replaces it, and the old secret stops working right away.
Tools like Clay ask you to send a token in a header instead. Add it when you create the webhook: "header": {"name": "x-clay-webhook-auth", "value": "your-token"}.
Delivery and retries
- Answer with any
2xxwithin 10 seconds. Do slow work after you respond. - Anything else (or a timeout) is retried after 1 minute, 5 minutes, 30 minutes, 2 hours, 6 hours and 12 hours. After that the event is marked
failedand the job is refunded. - Answering
410 Goneturns the webhook off at once. So does 72 hours in which every attempt failed. Turn it back on withPATCH /v2/webhooks/{id}and{"status": "active"}. - We send each webhook up to 50 events a minute, and don’t follow redirects. A bigger backlog goes out over the following minutes.
- See every event from the last 30 days, with what your endpoint answered, at
GET /v2/webhooks/{id}/deliveries(filter with?status=failed).
Pricing and limits
- Each event costs 1 job from your plan’s jobs allowance, the same as one Job Search result. Overage plans bill overage at the usual rate.
- Creating, listing, testing and estimating webhooks is free. Failed events are refunded, and so are events still unsent after 25 days (for example while you’ve paused the webhook).
max_jobs_per_day(default 1,000, up to 5,000) caps events per UTC day. Matches over the cap are skipped, not queued.- On plans that stop at their allowance, the webhook pauses when the allowance runs out and resumes by itself when it resets or you upgrade.
status_reasontells you why it’s paused. - Up to 10 webhooks per account. Webhooks use Job Search filters; Neural Search isn’t supported yet.
Using Clay, Zapier, Make or n8n
Create a webhook (or catch hook) trigger in the tool, copy its URL, and use it asurl. Each event arrives as one request, so each job or company becomes one row or one run. Keep your filters in the Hirebase search, not in the tool, so you only pay for jobs you want. Clay webhook sources accept 50,000 submissions each, so set max_jobs_per_day accordingly.
Get told when an export finishes
Export Jobs and Export Expired Jobs take an optionalnotify_url (https). When the export ends, we POST one signed event there instead of making you poll Get Task Status:
task.failed, with error set and result null. These events are signed the same way, but with your account secret, from GET /v2/webhooks/account-secret. You don’t need a webhook to use notify_url. A few quick retries are made, so keep polling as a fallback for anything critical.