Overview

imper.ai integrates with Workday Recruiting to receive real-time notifications when candidates enter and exit the Interview stage. This allows imper.ai to activate candidate identity protection exactly when it is needed - during interviews - and deactivate it automatically once interviews conclude.

The integration is lightweight by design. Workday sends a minimal webhook payload at two points in the hiring process; imper.ai pulls any additional candidate data separately via the Workday API.

---

How it works

Two Workday Orchestrate actions are added to the Job Application Business Process - one before the first interview stage, and one after the last.

Hook	Trigger	Purpose
Pre-interview	Candidate enters the first Interview stage	Signals imper.ai that interviews are starting for this candidate
Post-interview	Candidate exits the last Interview stage	Signals imper.ai that interviews have concluded

• Both hooks are configured as auto-complete steps - they fire silently in the background. Recruiters and hiring managers will not see any additional steps, inbox tasks, or UI changes. The existing recruiting workflow remains exactly as it is today.

• Because this is configured at theBP definition level , it applies globally to all job requisitions. No per-job or per-recruiter setup is required.

---

Webhook specification

Both hooks send an HTTPS POST request to the imper.ai endpoint with a small JSON payload.

Endpoint

POST https://api.prod.imper.ai/workday/webhooks/<orgID>/interview-stage

Authentication

An API key is passed as a request header:

Authorization: Bearer <API_KEY>

The API key is provided by imper.ai and should be stored securely in Workday - for example, encrypted within the Orchestration's credential configuration.

Request payload

{
 "event_type": "interview_started" | "interview_ended",
  "candidate_id": "WD-12345",
  "job_application_id": "JA-67890",
  "job_requisition_id": "JR-11111",
  "timestamp": "2026-04-09T14:30:00Z"
}

---

Field	Type	Description
event_type	string	interview_stage_started for the pre-interview hook; interview_stage_ended for the post-interview hook
candidate_id	string	The Workday Candidate ID (WID)
job_application_id	string	The Workday Job Application ID
job_requisition_id	string	The Workday Job Requisition ID
timestamp	string (ISO 8601)	When the stage transition occurred

NOTE

The payload is intentionally minimal. The candidate and application IDs are used to retrieve any additional data needed - candidate name, job profile, requisition details - via the Workday REST/SOAP API.

Expected response

Response	Meaning
200 OK	Webhook received successfully. The Orchestration step auto-completes and the business process continues.
4xx / 5xx	An error occurred. See Error Handling below.

---

Error handling

The Orchestration should be configured so that a failed webhook call does not block the business process.

If the imper.ai endpoint is unreachable or returns an error, the business process continues normally - recruiters are never blocked from moving candidates forward. Failed calls can be logged on the Workday side for retry or alerting.

---

Setup Steps

Your Workday integration team will need to complete the following:

1. Add two Orchestration steps to the Job Application BP - one before the first remote interview stage and one after the last.

2. Configure the HTTPS POST call per the specification above.

3. Store the API key(provided by imper.ai) in a secure credential store within Workday.

4. Set both steps to auto-complete so they are invisible to end users.

5. Configure error handling so failures do not block the recruiting process.

---

What imper.ai Provides

To support your integration team, imper.ai will supply:

1. The webhook endpoint URL for both production and sandbox/test environments

2. The API key for authentication

3. A test harness so the integration team can verify the connection before going live

4. API access coordination (ISU/OAuth setup) for pulling candidate data using the IDs from the webhook