Webhooks

Webhooks alert your external systems the moment a candidate takes action. Add your destination URL to subscribe to the following core events.

Set up outbound webhooks

Available webhook events

Event	Trigger	Use case
`interview.created`	A new interview record is created for a candidate.	Create or link the candidate interview in your ATS.
`interview.started`	The interview status changes to `in_progress`.	Mark the candidate as actively interviewing.
`interview.completed`	The interview status changes to `completed`.	Notify your team that the interview session has ended.
`interview.declined`	The interview status changes to `declined`.	Stop follow-ups and store the decline reason.
`interview.opted_out`	The interview status changes to `opted_out`.	Stop reminders and update the candidate’s consent status.
`interview.report_available`	`interview_feedback` is populated for the first time.	Start scorecard review or another downstream evaluation workflow.

interview.in_progress is a candidate status, not a webhook event. Subscribe to interview.started to receive that status change.

Event payloads

The webhook request body contains the event payload. Svix uses the selected event type to filter which endpoints receive it.

{
  "interviewId": "aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee",
  "jobId": "9786b00b-d110-454f-9e6f-1732daec8916",
  "name": "Jane Doe",
  "email": "jane@example.com",
  "status": "in_progress",
  "startedAt": "2026-08-12T10:15:00.000Z"
}

Every payload includes interviewId and jobId. The event-specific fields are:

Event	Additional payload fields
`interview.created`	`name`, `email`, `status`, `createdAt`
`interview.started`	`name`, `email`, `status`, `startedAt`
`interview.completed`	`name`, `email`, `status`, `completedAt`
`interview.declined`	`name`, `email`, `status`, `declineReason`, `declinedAt`
`interview.opted_out`	`name`, `email`, `status`, `optOutReason`, `optedOutAt`
`interview.report_available`	`name`, `email`, `status`, `reportGeneratedAt`, `trustScoreMetadata`, `trustScore`

Reasons and trust score fields can be null. All timestamps are ISO 8601 strings taken from the interview record.

Pre-launch checklist

API Key is generated and securely stored in your environment variables.
API Key is included in the header of all GET, POST, and PATCH requests.
Integration is configured for the correct, active Interviewer.
Webhook receiving endpoints are live and configured to accept POST requests.

Common mistakes to avoid

Missing headers: Forgetting to include the API key will result in 401 Unauthorized errors.
Ignoring retries: Failing to handle duplicate webhook events. Ensure your system processes webhook IDs idempotently.
Wrong Interviewer context: Pushing or fetching candidates from the wrong Interviewer ID.
Timeout failures: Webhook endpoint taking too long to respond. Always return a 200 OK status immediately before processing heavy data.

Custom Attributes: Managing Additional Fields

Getting Started

Main

Manage

Settings

Additional Platform Docs

For Candidates

Set up outbound webhooks

Available webhook events

Event payloads

Pre-launch checklist

​Set up outbound webhooks

​Available webhook events

​Event payloads

​Pre-launch checklist

Set up outbound webhooks

Available webhook events

Event payloads

Pre-launch checklist