Configure access
Use the candidate capability issued by the public application flow. Send Authorization: Candidate <token>, including the Candidate prefix. It is separate from staff and guest-portal credentials.
Candidate access is issued by the application flow; the public /candidate-portal page consumes the candidate capability. Recruiting administration remains at /organizations/:organizationId/workforce/recruiting, under workforce.recruiting.manage. The candidate token is not an administrator credential.
First successful workflow
Follow these steps in order. Open each method for its exact body, required headers and response schema.
- Read /me to obtain applications, interviews, offers and allowed actions.
- Withdraw an eligible owned application with a reason, or respond to an active owned offer.
- Use the returned application projection and revision to update the candidate interface.
State, retries and recovery
An expired offer or changed revision blocks the response. Withdrawal preserves submitted evidence and records a terminal stage; it does not delete the candidate’s history.