New application
Fire when a candidate submits an interview.
Send interview events to the systems you already run.
Configure a webhook per interview. Hirekal POSTs to your URL when a candidate submits, or when their stage changes.
Choose which events to send.
Webhooks are set on the interview. See all features. See webhooks in the docs.
Stage change
Fire when an applicant moves to a new stage.
Point Hirekal at a URL you control.
Add the webhook URL and a signing secret. Hirekal sends the payload to that address. You can pause delivery without deleting the endpoint.
See what was sent, then retry if needed.
Delivery logs show each attempt so you can confirm the event reached your system.
Signing secret
Each delivery includes an X-Hirekal-Signature header so your endpoint can verify the request.
Test, pause, and retry
Send a test delivery, enable or disable the webhook, and retry failed deliveries from the log.
Optional payload details
Include answers, video URLs, and transcripts in the payload when you need the full response.
Questions about webhooks.
Which events fire, how to verify a delivery, and how to retry.
Which events can an interview webhook send?
A new application when a candidate submits, and a stage change when an applicant moves to a new stage.
How do you verify a webhook delivery?
Each delivery includes an X-Hirekal-Signature header so your endpoint can confirm the request.
Can you retry a failed webhook?
Yes. The delivery log shows each attempt. You can send a test, pause the webhook, and retry failed deliveries.
Where do you set up a webhook?
On the interview. Hirekal POSTs to your URL when a candidate submits, or when their stage changes.
Can the webhook payload include the transcript?
Yes, if you include payload details. The payload can also include answers and video URLs.
Keep Hirekal in the recruiting tools you already use.
Receive new applications and stage changes at your own endpoint.