# Introduction

Cornerstone's new Candidate APIs provide the ability to get a requisition's full application workflow including prescreening questions, compliance questions, disclaimers, notes, and attachments. When utilized with the POST Candidate and Application Endpoint, applications may be posted in a complete or incomplete status. The GET Application Workflow is designed to work with the POST Candidate and Application endpoint to create a full candidate experience.

An example use of this GET endpoint:

  1. A chatbot provider is supporting a "chat to apply" experience and would like to create a candidate and application in Cornerstone
  2. You are hosting your own candidate experience via an alternate recruiting solution and would like to create a candidate and application in Cornerstone when the candidate submits their application
  3. An external job board would like to post applications to Cornerstone with answers to prescreening questions, compliance questions, and disclaimers An API consumer must know a requisition ID prior to retrieving an application workflow through the GET Application Workflow Endpoint. This can be found via the Get Job Requisition endpoint (information found here), a job distribution connector, or other source. The requisition must be in an 'open' or 'open pending re-approval' status and posted to at least one Cornerstone career site.

# Throttling

To ensure the best possible performance of the Candidate API for all Cornerstone clients, we have implemented throttle limits. Throttle limits apply to all authenticated APIs calls. If a request is made after the throttle limit is reached, an HTTP error is thrown, which is to be handled elegantly. We recommend that interface applications queue such requests until the throttle limit duration have passed and the request can be re-sent. If either the throttle limit or request frequency is exceeded, the following errors will be thrown, and must be handled. The GET Application Workflow endpoint will allow for 300 requests per minute.

# Returned Localization of the Application Workflow

When you request an application workflow from a requisition, the culture requested by the vendor should be based on the requestor's culture. For example, if I am a job applicant in Germany and have German as my default browser language, the integrator should take the job applicant's culture and make a request to CSOD for the application workflow in German.

In order to make this request, the integrator must pass a new header, called x-csod-accept-language. You can pass in any standard IETF language tag that CSOD supports to this header (available in the "Localization" section of the documentation here). For example, x-csod-accept-language = de-de. If a valid culture is not sent in the request, we will fallback to the integration user's culture.

There are a few scenarios to note, as listed below. For all of the examples below, let's assume the applicant has a default browser language in German and the application workflow was created in English.

  • All Application Workflow Action Items are available in requested culture
    • In this scenario, the request for the application workflow is in German and all application workflow action items are available in German. The response will retrieve all action items in German and the candidate will apply in German.
  • No Application Workflow Action items are available in German, but they all are available in English
    • In this scenario none of the application workflow action items had a German translation configured by the organization. However, because the application workflow was created in English, and all action items have an English translation, the applicant will receive the application workflow action items in English. This logic was implemented so that if the applicant's default language is not supported, it provides for the best chance of consistency for the applicant to have all action items translated to the same language.
  • Some Application Workflow Action Items are available in German, some do not have a German translation, but have an English translation, and one action item that does not have a German nor an English translation.
    • In this scenario let's assume the Application Workflow consists of:
      • 3 PSQs that have a German translation
      • 1 Note that has an English and Arabic translation
      • 1 Disclaimer that was created in Italian and never configured to have any other translations.
    • In this scenario because the applicant requested in German, the PSQs will appear in German, the Note will appear in English (as that is the language of the creation of the Application Workflow), and the Disclaimer will appear in Italian.

It is critical that organizations ensure that their application workflows have all the proper translations for the candidates that will apply for their jobs, so that there is a consistent experience for the applicant.

# Pre-Screening Question Scoring

Pre-screening scoring information is not available via the GET Application Workflow endpoint. The calculations of a candidate's score for pre-screening questions will be done via the POST endpoint upon submission of an application. Additionally, we will not include details as to whether the pre-screening question is a knockout or not. This will also be done via the POST endpoint upon submission.

# Permissions Required

No new permissions are required to leverage the GET Application Workflow endpoint. However the following existing permissions apply to enablement:

  • Edge Integrations–Manage: Grants access to the Integrations service for Edge Integrate where the administrator can configure, enable, and disable their third-party integrations that are used within the Cornerstone system. This permission cannot be constrained. This is an administrator permission
  • Edge Marketplace–Manage: Grants access to the Marketplace service for Edge Integrate where the administrator can browse and purchase integrations that can be used to extend the Cornerstone system. This permission cannot be constrained. This is an administrator permission.