Webhook Event Types - Taptalent Partner API

TapTalent sends webhook events for various operations. All webhook payloads follow a consistent structure.

Payload structure

Every webhook body looks like:

{
  "event": "event.type.name",
  "timestamp": "2024-01-20T14:45:00Z",
  "companyId": 12345,
  "data": {
    // Event-specific data
  }
}

Field	Type	Description
`event`	string	The event type (e.g. `candidate.updated`)
`timestamp`	string	ISO 8601 UTC timestamp when the event occurred
`companyId`	integer	The TapTalent company ID the event belongs to
`data`	object	Event-specific payload (see each event below)

Headers

All webhook requests include:

Content-Type: application/json
X-Webhook-Event: The event type (e.g. resume.bulk_upload_parse.started)
X-Webhook-Timestamp: ISO 8601 timestamp of when the event occurred
X-Webhook-Key: Your webhook verification secret. When you have generated a webhook key in the dashboard, TapTalent sends it in this header. Compare it to your stored key to verify the request came from TapTalent. If no key has been set, the header may be empty.

Resume events

`resume.bulk_upload_parse.started`

Triggered when a bulk resume upload batch starts processing.

{
  "event": "resume.bulk_upload_parse.started",
  "timestamp": "2024-01-20T14:45:00Z",
  "data": {
    "batchId": 12345,
    "fileCount": 25,
    "jobId": 12345
  }
}

Field	Type	Description
`batchId`	integer	The batch ID for this upload
`fileCount`	number	Total number of resumes in the batch
`jobId`	integer or null	The job ID if resumes were uploaded to a specific job, otherwise `null`

`resume.bulk_upload_parse.completed`

Triggered when a bulk resume upload batch completes processing.

{
  "event": "resume.bulk_upload_parse.completed",
  "timestamp": "2024-01-20T14:45:00Z",
  "data": {
    "batchId": 12345,
    "status": "COMPLETED",
    "fileCount": 25,
    "successCount": 23,
    "failedCount": 2,
    "jobId": 12345
  }
}

Field	Type	Description
`batchId`	integer	The batch ID for this upload
`status`	string	Batch processing status (e.g. “COMPLETED”)
`fileCount`	number	Total number of resumes in the batch
`successCount`	number	Number of resumes successfully parsed
`failedCount`	number	Number of resumes that failed to parse
`jobId`	integer or null	The job ID if resumes were uploaded to a specific job, otherwise `null`

`resume.bulk_upload_parse.failed`

Triggered when a bulk resume upload batch fails before processing begins (e.g. validation errors, invalid URLs).

{
  "event": "resume.bulk_upload_parse.failed",
  "timestamp": "2024-01-20T14:45:00Z",
  "data": {
    "error": "Error message describing the failure"
  }
}

Field	Type	Description
`error`	string	Error message describing why the batch failed

Job events (recruiter actions)

`job.created`

Triggered when a recruiter creates a new job from the dashboard.

{
  "event": "job.created",
  "timestamp": "2024-01-20T14:45:00Z",
  "data": {
    "jobId": 12345,
    "title": "Software Engineer"
  }
}

`job.updated`

Triggered when a recruiter updates a job’s basic details (e.g. title, description, location) from the dashboard. Does not fire when only the job status is changed.

{
  "event": "job.updated",
  "timestamp": "2024-01-20T14:45:00Z",
  "data": {
    "jobId": 12345,
    "updatedFields": ["title", "description", "city"]
  }
}

`job.status_changed`

Triggered when a recruiter changes a job’s status (e.g. Draft → Active, Active → Inactive/Closed).

{
  "event": "job.status_changed",
  "timestamp": "2024-01-20T14:45:00Z",
  "data": {
    "jobId": 12345,
    "status": "INACTIVE",
    "previousStatus": "ACTIVE",
    "closingStatus": "Filled",
    "closingReason": "Position filled internally"
  }
}

Field	Type	Description
`jobId`	integer	The job ID
`status`	string	New status (e.g. `ACTIVE`, `INACTIVE`, `DRAFT`)
`previousStatus`	string or null	Status before the change
`closingStatus`	string or null	If the job was closed, the selected closing reason (e.g. Filled, Cancelled)
`closingReason`	string or null	Optional text or detail for the closing

Candidate events (recruiter actions)

`candidate.added_to_job`

Triggered when a recruiter adds one or more candidates to a job (e.g. from company list, AI search, or moving from another job).

{
  "event": "candidate.added_to_job",
  "timestamp": "2024-01-20T14:45:00Z",
  "data": {
    "jobId": 12345,
    "stageId": 2,
    "candidateIds": ["candidateId-1", "candidateId-2"],
    "jobCandidateIds": [101, 102],
    "count": 2
  }
}

Field	Type	Description
`jobId`	integer	The job the candidates were added to
`stageId`	integer	The pipeline stage ID (optional in payload)
`candidateIds`	array	Candidate IDs that were added
`jobCandidateIds`	array	Job–candidate record IDs for each added candidate
`count`	number	Number of candidates added

`candidate.stage_changed`

Triggered when a recruiter moves one or more candidates to a different pipeline stage (e.g. kanban drag-and-drop).

{
  "event": "candidate.stage_changed",
  "timestamp": "2024-01-20T14:45:00Z",
  "data": {
    "jobId": 12345,
    "currentStageId": 2,
    "nextStageId": 3,
    "jobCandidateIds": [101, 102],
    "candidateIds": ["candidateId_1", "candidateId_2"]
  }
}

`candidate.hired`

Triggered when a recruiter moves one or more candidates to the Hired stage.

{
  "event": "candidate.hired",
  "timestamp": "2024-01-20T14:45:00Z",
  "data": {
    "jobId": 12345,
    "jobCandidateIds": [101, 102],
    "candidateIds": ["candidateId_1", "candidateId_2"]
  }
}

`candidate.rejected`

Triggered when a recruiter rejects or disqualifies one or more candidates, or when an automated screening flow disqualifies a candidate.

{
  "event": "candidate.rejected",
  "timestamp": "2024-01-20T14:45:00Z",
  "data": {
    "jobId": 12345,
    "jobCandidateIds": [101],
    "candidateIds": ["candidateId_1"],
    "jobCandidateId": 101,
    "candidateId": "candidateId_1",
    "reason": "Automated screening flow rejected."
  }
}

`candidate.removed_from_job`

Triggered when one or more candidates are removed from a job. This is sent when:

A recruiter uses the bulk “Remove from job” / “Delete” action on candidates in that job (move-job-candidates with delete), or
A recruiter deletes one or more candidates from the company (DELETE /candidates), in which case one event is sent per job those candidates were in.

{
  "event": "candidate.removed_from_job",
  "timestamp": "2024-01-20T14:45:00Z",
  "data": {
    "jobId": 12345,
    "jobCandidateIds": [101, 102],
    "candidateIds": ["candidateId_1", "candidateId_2"]
  }
}

Field	Type	Description
`jobId`	integer	The job the candidates were removed from
`jobCandidateIds`	array	Job–candidate record IDs that were removed
`candidateIds`	array	Candidate IDs that were removed from the job

`candidate.updated`

Triggered when a recruiter updates a candidate’s profile or job-application details from the dashboard.

Profile (scope: "profile"): Company-level profile (e.g. name, email, phone, resume, skills) via Update company candidate details or Update job candidate details (email/phone).
Application (scope: "application"): Application for a specific job (e.g. expected CTC, notice period, hired date) via Update job candidate application.

Profile update example:

{
  "event": "candidate.updated",
  "timestamp": "2024-01-20T14:45:00Z",
  "data": {
    "candidateId": "candidateId_1",
    "updatedFields": ["firstName", "email", "phone"],
    "scope": "profile"
  }
}

Application update example (includes jobCandidateId and jobId):

{
  "event": "candidate.updated",
  "timestamp": "2024-01-20T14:45:00Z",
  "data": {
    "jobCandidateId": 101,
    "jobId": 12345,
    "candidateId": "candidateId_1",
    "updatedFields": ["expectedCTC", "noticePeriod"],
    "scope": "application"
  }
}

Application events

Events for candidate applications submitted through the TapTalent-hosted application experience. See Candidate Applications.

`candidate.applied`

Triggered when a candidate submits an application on the TapTalent-hosted application experience for a job. Fires once per submission (never batched). The job candidate is created at the pipeline’s APPLIED stage.

{
  "event": "candidate.applied",
  "timestamp": "2024-01-20T14:45:00Z",
  "companyId": 12345,
  "data": {
    "jobId": 12345,
    "jobCandidateId": 101,
    "candidateId": "candidateId_1",
    "stageId": 2,
    "candidate": { "firstName": "John", "lastName": "Doe", "email": "john.doe@example.com", "phone": "+639171234567" },
    "resumeUrl": "https://cdn.taptalent.io/applications/101/resume.pdf?signature=...",
    "appliedAt": 1705761900000,
    "screeningQuestionAnswer": [
      { "question": "How many years of experience do you have with Node.js?", "answer": "6 years" }
    ],
    "consent": {
      "acceptedAt": 1705761890000,
      "policyVersion": "2025-08",
      "consentDocumentUrl": "https://cdn.taptalent.io/applications/101/dpa-acknowledgment.pdf?signature=...",
      "expiresAt": 1705765500000
    }
  }
}

Field	Type	Description
`jobId`	number	The job applied to
`jobCandidateId`	number	The job-candidate record created by the application
`candidateId`	string	The candidate ID
`stageId`	number	The APPLIED stage the candidate landed in (resolve names/types via Pipelines)
`candidate`	object	`firstName`, `lastName`, `email`, `phone` (`phone` is `null` when not collected)
`resumeUrl`	string or null	Time-limited URL to the submitted resume; re-fetch via Get Application Details
`appliedAt`	number	Unix timestamp (ms) of the submission
`screeningQuestionAnswer`	array	`{question, answer}` pairs; empty when the job has no screening questions
`consent`	object or null	`acceptedAt`, `policyVersion`, time-limited `consentDocumentUrl`, `expiresAt`; re-fetch via Get Consent Document; `null` for applications that predate consent capture

After candidate.applied, resume parsing and AI scoring run and job.candidate.score.completed (or .failed) follows for the same jobCandidateId. If the job has screening automation configured, it may then emit candidate.stage_changed or candidate.rejected. Note that candidate.applied is always per-candidate, while candidate.stage_changed remains batched.

Job candidate scoring events

`job.candidate.score.completed`

Triggered when AI scoring is completed for a candidate’s application to a job. This event is sent after the candidate’s resume has been analyzed and matched against the job requirements, and a score has been calculated.

{
  "event": "job.candidate.score.completed",
  "timestamp": "2024-01-20T14:45:00Z",
  "data": {
    "jobId": 12345,
    "jobCandidateId": 101,
    "candidateId": "candidateId_1",
    "score": 85.5
  }
}

Field	Type	Description
`jobId`	integer	The job ID the candidate applied to
`jobCandidateId`	integer	The job–candidate record ID
`candidateId`	string	The candidate ID
`score`	number	The AI-generated match score (typically 0-100) representing how well the candidate matches the job requirements

`job.candidate.score.failed`

Triggered when AI scoring fails for a candidate’s application to a job. This event is sent when the scoring process encounters an error (e.g. insufficient candidate data, processing error, or service unavailability).

{
  "event": "job.candidate.score.failed",
  "timestamp": "2024-01-20T14:45:00Z",
  "data": {
    "jobId": 12345,
    "jobCandidateId": 101,
    "candidateId": "candidateId_1",
    "error": "Scoring failed: insufficient candidate data"
  }
}

Field	Type	Description
`jobId`	integer	The job ID the candidate applied to
`jobCandidateId`	integer	The job–candidate record ID
`candidateId`	string	The candidate ID
`error`	string	Error message describing why scoring failed

Assessment events

`assessment.ready`

Triggered when questions have been generated for an assessment (e.g. after Auto-Generate Assessment or Generate Questions). You can then fetch the assessment or invite candidates.

{
  "event": "assessment.ready",
  "timestamp": "2024-01-20T14:45:00Z",
  "data": {
    "assessmentId": "assessmentId_1",
    "message": "Assessment questions generated and ready",
    "questionCount": 5
  }
}

Field	Type	Description
`assessmentId`	string	The assessment ID
`message`	string	Confirmation message
`questionCount`	number	Number of questions added to the assessment

`assessment.bulk_invite.completed`

Triggered when processing finishes for a bulk invite batch. Fetch per-candidate outcomes from Get Bulk Invite Status.

{
  "event": "assessment.bulk_invite.completed",
  "timestamp": "2024-01-20T14:45:00Z",
  "companyId": 12345,
  "data": {
    "assessmentId": "assessmentId_1",
    "batchId": "inviteBatchId_1",
    "totalCount": 250,
    "invitedCount": 245,
    "skippedCount": 3,
    "failedCount": 2
  }
}

Field	Type	Description
`assessmentId`	string	The assessment ID
`batchId`	string	The bulk invite batch ID
`totalCount`	number	Total entries in the batch
`invitedCount`	number	Entries successfully invited
`skippedCount`	number	Entries skipped (already invited)
`failedCount`	number	Entries that could not be invited

`interview.started`

Triggered when a candidate has started an assessment interview (e.g. opened the interview and it has begun). Use this to track when invited candidates begin their assessment.

{
  "event": "interview.started",
  "timestamp": "2024-01-20T14:45:00Z",
  "companyId": "company_id_12345",
  "data": {
    "assessmentId": "assessmentId_1",
    "submissionId": "submissionId_1",
    "interviewStatus": "STARTED",
    "firstName": "John",
    "lastName": "Doe",
    "email": "john.doe@example.com",
    "jobCandidateId": 101,
    "externalRef": "REQ-2025-0042/C-001"
  }
}

Field	Type	Description
`assessmentId`	string	The assessment ID
`submissionId`	string	The interview submission ID
`interviewStatus`	string	Status of the interview (e.g. `STARTED`)
`firstName`	string	Candidate’s first name (if available)
`lastName`	string	Candidate’s last name (if available)
`email`	string	Candidate’s email (if available)
`jobCandidateId`	number or null	Job-candidate ID if the candidate was invited via a job (optional)
`externalRef`	string or null	Reference supplied on the invite via Bulk Invite Candidates; `null` when none was provided

`interview.scoring_completed`

Triggered when scoring has finished for an interview submission. Use this to sync results to your system, fetch the result report PDF or public result link, or notify recruiters.

{
  "event": "interview.scoring_completed",
  "timestamp": "2024-01-20T15:00:00Z",
  "companyId": 12345,
  "data": {
    "assessmentId": "assessmentId_1",
    "submissionId": "submissionId_1",
    "status": "COMPLETED",
    "score": 78,
    "bucket": "Good Fit",
    "firstName": "John",
    "lastName": "Doe",
    "email": "john.doe@example.com",
    "jobCandidateId": 101,
    "externalRef": "REQ-2025-0042/C-001"
  }
}

Field	Type	Description
`assessmentId`	string	The assessment ID
`submissionId`	string	The interview submission ID
`status`	string	Status (e.g. `COMPLETED`)
`score`	number	Overall score for the submission
`bucket`	string or null	Evaluation bucket (e.g. “Strong Fit”, “Good Fit”) if configured
`firstName`	string	Candidate’s first name (if available)
`lastName`	string	Candidate’s last name (if available)
`email`	string	Candidate’s email (if available)
`jobCandidateId`	number or null	Job-candidate ID if linked to a job (optional)
`externalRef`	string or null	Reference supplied on the invite via Bulk Invite Candidates; `null` when none was provided

`interview.ended`

Triggered when a candidate has finished or left the interview (e.g. completed all questions, timed out, or ended the session). Use this to track completion and optionally wait for interview.scoring_completed for the final score.

{
  "event": "interview.ended",
  "timestamp": "2024-01-20T14:55:00Z",
  "companyId": 12345,
  "data": {
    "assessmentId": "assessmentId_1",
    "submissionId": "submissionId_1",
    "status": "FINISHED",
    "firstName": "John",
    "lastName": "Doe",
    "email": "john.doe@example.com",
    "jobCandidateId": 101,
    "externalRef": "REQ-2025-0042/C-001"
  }
}

Field	Type	Description
`assessmentId`	string	The assessment ID
`submissionId`	string	The interview submission ID
`status`	string	Status (e.g. `FINISHED`)
`firstName`	string	Candidate’s first name (if available)
`lastName`	string	Candidate’s last name (if available)
`email`	string	Candidate’s email (if available)
`jobCandidateId`	number or null	Job-candidate ID if linked to a job (optional)
`externalRef`	string or null	Reference supplied on the invite via Bulk Invite Candidates; `null` when none was provided

`interview.error`

Triggered when an error occurs during the interview flow (e.g. failed to start, scoring failure, or permission issues). Use this to monitor failures and alert or retry as needed.

{
  "event": "interview.error",
  "timestamp": "2024-01-20T14:46:00Z",
  "companyId": 12345,
  "data": {
    "assessmentId": "assessmentId_1",
    "submissionId": "submissionId_1",
    "externalRef": "REQ-2025-0042/C-001",
    "errorType": "START_FAILED",
    "errorMessage": "Failed to start interview",
    "timestamp": 1708363560000
  }
}

Field	Type	Description
`assessmentId`	string	The assessment ID
`submissionId`	string or null	The interview submission ID (if one was created)
`externalRef`	string or null	Reference supplied on the invite via Bulk Invite Candidates; `null` when none was provided
`errorType`	string	Error category (e.g. `START_FAILED`, `SCORING_FAILED`, `AUDIO_PERMISSION_DENIED`)
`errorMessage`	string	Human-readable error message
`timestamp`	number	Unix timestamp when the error occurred

`interview.complete_later`

Triggered when a candidate clicks “Complete later (not recommended)” on the pre-interview setup screen. The candidate has chosen to save their link and finish the assessment later instead of starting now.

{
  "event": "interview.complete_later",
  "timestamp": "2024-01-20T14:50:00Z",
  "companyId": 12345,
  "data": {
    "assessmentId": "assessmentId_1",
    "firstName": "John",
    "lastName": "Doe",
    "email": "john.doe@example.com",
    "jobCandidateId": 101,
    "externalRef": "REQ-2025-0042/C-001",
    "timestamp": 1708363800000
  }
}

Field	Type	Description
`assessmentId`	string	The assessment ID
`firstName`	string	Candidate’s first name (if available)
`lastName`	string	Candidate’s last name (if available)
`email`	string	Candidate’s email (if available)
`jobCandidateId`	number or null	Job-candidate ID if linked to a job (optional)
`externalRef`	string or null	Reference supplied on the invite via Bulk Invite Candidates; `null` when none was provided
`timestamp`	number	Unix timestamp when the candidate chose complete later

Agentic Onboarding events

Events for the Agentic Onboarding API. All report and document files are PDFs delivered as time-limited URLs—download promptly, or re-fetch fresh URLs from List Candidate Documents and Reports.

`onboarding.candidate.enrolled`

Triggered when a candidate is enrolled into an onboarding flow (fires once per candidate, including bulk enrollments). Use this to store the onboardingCandidateId against your own candidate record.

{
  "event": "onboarding.candidate.enrolled",
  "timestamp": "2024-01-20T14:45:00Z",
  "companyId": 12345,
  "data": {
    "onboardingCandidateId": "onbCandidateId_1",
    "flowId": "flowId_1",
    "flowName": "New Hire Onboarding",
    "externalRef": "CAND-88213",
    "overallStatus": "not_started",
    "candidate": { "firstName": "John", "lastName": "Doe", "email": "john.doe@example.com" }
  }
}

Field	Type	Description
`onboardingCandidateId`	string	The onboarding candidate ID
`flowId`	string	The onboarding flow ID
`flowName`	string	The onboarding flow name
`externalRef`	string or null	Reference supplied at enrollment; `null` when none was provided
`overallStatus`	string	Candidate status at enrollment (`not_started`)
`candidate`	object	Candidate identity (`firstName`, `lastName`, `email`)

`onboarding.candidate.status_changed`

Triggered when a candidate’s overallStatus changes, including terminal states (completed, rejected, failed, terminated). Use this to move the candidate’s status in your system of record where your process requires it.

{
  "event": "onboarding.candidate.status_changed",
  "timestamp": "2024-01-20T15:00:00Z",
  "companyId": 12345,
  "data": {
    "onboardingCandidateId": "onbCandidateId_1",
    "externalRef": "CAND-88213",
    "previousStatus": "in_progress",
    "status": "under_review",
    "stepKey": "background_verification",
    "changedAt": 1708363800000
  }
}

Field	Type	Description
`onboardingCandidateId`	string	The onboarding candidate ID
`externalRef`	string or null	Reference supplied at enrollment; `null` when none was provided
`previousStatus`	string	Status before the change
`status`	string	New status (`not_started`, `in_progress`, `partial_submission`, `under_review`, `final_handoff`, `completed`, `rejected`, `failed`, `terminated`)
`stepKey`	string or null	Flow step that triggered the change, if any
`changedAt`	number	Unix timestamp of the change

`onboarding.documents.verified`

Triggered when a candidate’s government documents and numbers have been validated during pre-onboarding. Use the PDF URLs and extracted fields to upload the documents to the candidate’s record in your system.

{
  "event": "onboarding.documents.verified",
  "timestamp": "2024-01-20T15:10:00Z",
  "companyId": 12345,
  "data": {
    "onboardingCandidateId": "onbCandidateId_1",
    "externalRef": "CAND-88213",
    "stepKey": "doc_collection",
    "documents": [
      {
        "documentId": "documentId_1",
        "name": "Government ID",
        "category": "government_document",
        "pdfUrl": "https://cdn.taptalent.io/onboarding/onbCandidateId_1/documentId_1.pdf?signature=...",
        "extractedFields": { "idNumber": "12-3456789-0" }
      }
    ]
  }
}

Field	Type	Description
`onboardingCandidateId`	string	The onboarding candidate ID
`externalRef`	string or null	Reference supplied at enrollment; `null` when none was provided
`stepKey`	string	Flow step the documents belong to
`documents`	array	Verified documents: `documentId`, `name`, `category`, time-limited `pdfUrl`, OCR `extractedFields`

`onboarding.report.ready`

Triggered every time a report PDF becomes available: a background verification report (initial or final), a pre-employment medical result, or a medical clearance slip. Use the PDF URL to upload and tag the report in your system of record.

{
  "event": "onboarding.report.ready",
  "timestamp": "2024-01-20T16:00:00Z",
  "companyId": 12345,
  "data": {
    "onboardingCandidateId": "onbCandidateId_1",
    "externalRef": "CAND-88213",
    "reportType": "BACKGROUND_VERIFICATION",
    "reportStage": "final",
    "stepKey": "background_verification",
    "report": {
      "documentId": "documentId_2",
      "name": "Background Verification Report - Final",
      "pdfUrl": "https://cdn.taptalent.io/onboarding/onbCandidateId_1/documentId_2.pdf?signature=...",
      "expiresAt": 1708450200000
    }
  }
}

Field	Type	Description
`onboardingCandidateId`	string	The onboarding candidate ID
`externalRef`	string or null	Reference supplied at enrollment; `null` when none was provided
`reportType`	string	`BACKGROUND_VERIFICATION`, `PRE_EMPLOYMENT_MEDICAL`, or `MEDICAL_CLEARANCE`
`reportStage`	string or null	`initial` or `final` for background verification reports; `null` otherwise
`stepKey`	string	Flow step the report belongs to
`report`	object	The report: `documentId`, `name`, time-limited `pdfUrl`, `expiresAt` (Unix timestamp, ms)

`onboarding.candidate.completed`

Triggered when a candidate reaches completed after final validation. Carries the final document package; use it to upload the package and finalize the hire in your system. A onboarding.candidate.status_changed event is also emitted for the same transition—key your terminal handling off this event and de-duplicate.

{
  "event": "onboarding.candidate.completed",
  "timestamp": "2024-01-25T10:00:00Z",
  "companyId": 12345,
  "data": {
    "onboardingCandidateId": "onbCandidateId_1",
    "externalRef": "CAND-88213",
    "completedAt": 1708855200000,
    "documentPackage": [
      {
        "documentId": "documentId_3",
        "name": "Employment Records Package",
        "category": "document_package",
        "pdfUrl": "https://cdn.taptalent.io/onboarding/onbCandidateId_1/documentId_3.pdf?signature=..."
      }
    ]
  }
}

Field	Type	Description
`onboardingCandidateId`	string	The onboarding candidate ID
`externalRef`	string or null	Reference supplied at enrollment; `null` when none was provided
`completedAt`	number	Unix timestamp when the candidate completed onboarding
`documentPackage`	array	Final document package: `documentId`, `name`, `category`, time-limited `pdfUrl` per document

`onboarding.offer.completed`

Triggered when every signer on an offer document has signed and the final signed PDF and audit certificate are ready. Use it to file the signed offer letter against the candidate in your system of record. This is the only offer event—for interim signer progress, poll Get Offer Document.

{
  "event": "onboarding.offer.completed",
  "timestamp": "2024-01-20T14:45:00Z",
  "companyId": 12345,
  "data": {
    "offerId": "offerId_1",
    "subject": "Offer Letter - Senior Software Engineer",
    "jobCandidateId": 101,
    "candidateId": "candidateId_1",
    "jobId": 12345,
    "completedAt": 1708363800000,
    "signedPdfUrl": "https://cdn.taptalent.io/offers/offerId_1/signed.pdf?signature=...",
    "auditTrailUrl": "https://cdn.taptalent.io/offers/offerId_1/audit-certificate.pdf?signature=...",
    "expiresAt": 1708450200000,
    "signers": [
      { "name": "John Doe", "email": "john.doe@example.com", "signedAt": 1708363700000 },
      { "name": "Jane Smith", "email": "jane.smith@example.com", "signedAt": 1708363800000 }
    ]
  }
}

Field	Type	Description
`offerId`	string	The offer document ID—use it with Get Offer Document
`subject`	string	The document’s subject line
`jobCandidateId`	number or null	Job-candidate ID from the candidate signer; `null` when the document is not linked to a job candidate
`candidateId`	string or null	Candidate ID from the candidate signer; `null` when not linked
`jobId`	number or null	The job the linked job candidate belongs to; `null` when not linked
`completedAt`	number	Unix timestamp (ms) when the last signer signed
`signedPdfUrl`	string	Time-limited URL to the final signed PDF (includes the audit-trail certificate)
`auditTrailUrl`	string	Time-limited URL to the standalone audit certificate PDF
`expiresAt`	number	Unix timestamp (ms) when the URLs expire—re-fetch fresh URLs from Get Offer Document
`signers`	array	Who signed: `name`, `email`, `signedAt` (Unix timestamp, ms) per signer

More event types may be added in future releases. Check this page for updates.

​Payload structure

​Headers

​Resume events

​resume.bulk_upload_parse.started

​resume.bulk_upload_parse.completed

​resume.bulk_upload_parse.failed

​Job events (recruiter actions)

​job.created

​job.updated

​job.status_changed

​Candidate events (recruiter actions)

​candidate.added_to_job

​candidate.stage_changed

​candidate.hired

​candidate.rejected

​candidate.removed_from_job

​candidate.updated

​Application events

​candidate.applied

​Job candidate scoring events

​job.candidate.score.completed

​job.candidate.score.failed

​Assessment events

​assessment.ready

​assessment.bulk_invite.completed

​interview.started

​interview.scoring_completed

​interview.ended

​interview.error

​interview.complete_later

​Agentic Onboarding events

​onboarding.candidate.enrolled

​onboarding.candidate.status_changed

​onboarding.documents.verified

​onboarding.report.ready

​onboarding.candidate.completed

​onboarding.offer.completed

Payload structure

Headers

Resume events

`resume.bulk_upload_parse.started`

`resume.bulk_upload_parse.completed`

`resume.bulk_upload_parse.failed`

Job events (recruiter actions)

`job.created`

`job.updated`

`job.status_changed`

Candidate events (recruiter actions)

`candidate.added_to_job`

`candidate.stage_changed`

`candidate.hired`

`candidate.rejected`

`candidate.removed_from_job`

`candidate.updated`

Application events

`candidate.applied`

Job candidate scoring events

`job.candidate.score.completed`

`job.candidate.score.failed`

Assessment events

`assessment.ready`

`assessment.bulk_invite.completed`

`interview.started`

`interview.scoring_completed`

`interview.ended`

`interview.error`

`interview.complete_later`

Agentic Onboarding events

`onboarding.candidate.enrolled`

`onboarding.candidate.status_changed`

`onboarding.documents.verified`

`onboarding.report.ready`

`onboarding.candidate.completed`

`onboarding.offer.completed`