Skip to main content
When something happens with a Candidate, InterviewFlowAI sends a POST request with a JSON body to each endpoint subscribed to that event. Turn webhooks on for an Interviewer in the dashboard (see Webhooks) or with webhookConfig when you create an Interviewer.

Events

Each endpoint gets only the events it subscribed to.

Data in each event

Every event has the same base fields. Each event then adds its own. All timestamps are ISO 8601 strings in UTC. metadata gives back what you sent when you invited the Candidate, such as your ATS ID. Use it to match the event to your own record.

interview.created

interview.started

interview.completed

The score isn’t ready yet. Wait for interview.report_available.

interview.declined

interview.opted_out

interview.report_available

Sent once, the first time the report is ready.

assessment.shortlisted, assessment.started, assessment.completed

Zapier

Zapier gets the same data for each event.

What can change

We only add to these events: new events and new fields. We never remove, rename or retype a field. Your code should ignore fields it doesn’t know.

Receive events

  • Respond fast. Return a 2xx status right away, then do slow work in the background. Failed deliveries are retried.
  • Expect duplicates. Retries can deliver the same event more than once. A retry keeps the same svix-id header as the first attempt, so store the IDs you’ve processed and skip any you’ve seen before.
  • Verify the signature. Each request carries svix-id, svix-timestamp and svix-signature headers, signed with your endpoint’s secret (whsec_…). Find the secret under Manage on the Interviewer’s Integrations tab, or in webhookConfig.secret when you create an Interviewer with the API. Verify with the Svix libraries before you trust the body.