Skip to main content
For general webhook concepts like bubble-up behavior, payload visibility rules, and versioned snapshots, see Webhook Concepts.

Description

This event is triggered when a candidate’s profile is updated, or when any subordinate record changes (education, experience, attachments, etc.) — all changes bubble up to the candidate root.

Integration Details

  • Subscription Key: can.candidate.updated
  • Use Case: Keep candidate data in sync with your ATS or external systems.
  • Related Events: can.candidate.created

Trigger

  • Event Type: can_candidate_updated
  • Source: Update of a record in the can.candidate table, or bubble-up from subordinate changes to any of the candidate’s nested records (attachments, contacts, education, experiences, certifications, projects, skill proficiencies, social media links, calendars, preferred locations).

Payload Example

Payload Type Showcase

Field Notes

  • cf (custom fields) and meta are JSONB — shape varies per tenant configuration.
  • responsibilities and tools_used on experiences are JSONB arrays.
  • evidence_snippet on skill proficiencies is JSONB containing parsed resume excerpts.
  • location on preferred_locations is JSONB with structured geo data.
  • projects nests technologies as a second-level subordinate.
  • file_type_id on attachments references a lookup enum to distinguish resumes, certificates, etc.
  • All subordinate arrays are pre-filtered to exclude soft-deleted records.