Configure access
The organization’s recruiting administrator publishes an active posting for an open requisition. Share its publicSlug and current privacy-notice version with the application flow.
Cabinet route: /organizations/:organizationId/workforce/recruiting. Publishing and managing the posting requires workforce.recruiting.manage. Public reading and applying do not require an account session.
First successful workflow
Follow these steps in order. Open each method for its exact body, required headers and response schema.
- GET the posting and display the role and current privacy notice.
- POST the applicant details and submission key after consent.
- Keep the returned application identity, candidate token and expiry; offer the candidate portal as the next step.
State, retries and recovery
Only active, published, unexpired postings with an open requisition accept applications. An identical submission key can return an already committed application. The created application starts at APPLIED; it does not mean the candidate is hired.