JobApplicationContract schema definitions (v2.1)
2 schema types · Source: schemas-main
Metadata about a document submitted by the candidate during the application process. Document content is never carried inside Beckn messages — only a reference pointer and verification status are stored. Separating submitted_documents into a structured array (rather than a free-text notes field) enables network-level automation of document checklist completion tracking.
Pipeline state and lifecycle metadata for a job application contract. Models the full arc from application submission through offer acceptance to onboarding. Structured document tracking (submitted_documents) replaces free-text document notes to enable automated checklist verification. The offer_status and onboarding_status fields are explicit enumerations so BAP and BPP can drive workflow state machines without parsing free text. employee_id is disclosed only post-acceptance (MUST NOT appear before ACCEPTED stage).