An API consumer must know a requisition ID prior to requesting an application workflow, and creating a candidate or application. This can be found via the Get Job Requisition endpoint (information found here), a job distribution connector, or other source.
A requisition must be in an 'open' or 'open pending re-approval' status and posted to at least one Cornerstone career site in order for an application and candidate to be added via the POST Application and Candidate endpoint. The requisition posting should also be active at the time of application submission. Requisitions must be posted to a career site so that an applicant can finish an application when invited to do so by a recruiter.
If your applications, or your client's applications consist of more than a resume and cover letter, and frequently include prescreening questions, compliance questions or disclaimers, we recommend writing to our new POST Application and Candidate endpoint, rather than our legacy Job Application API. Cornerstone's new POST Application and Candidate endpoint is flexible and allows API consumers to post as little as a candidate's first name, last name, and email, or as much as the full application without validating against the job requisition. It is up to the API consumer to validate against required application questions. We have no plans to deprecate the legacy Job Application API, as select vendors only post a resume and cover letter to Cornerstone.
While not required, API consumers may also call Cornerstone's Employee Global Search API to determine if a candidate is an internal or external candidate (documentation found here). This will enable the API consumer to request the correct application workflow- Internal or External.
