Some organizations aren’t able to build the candidate export integration with the candidate-hired webhook because the HRIS or integration partner does not have a listener service that can accept webhooks. To get around this issue, you can pull data from the API instead of leveraging Greenhouse Recruiting webhooks.
API request steps
GET List Offers using the
- This method will return the
job_idthat you need to retrieve the application, candidate, and job data
Status=acceptedensures that all returned candidates have been hired
Resolved_after=[date/time]ensures that the integration is only pulling offers that were marked as accepted since the last time the integration polled Greenhouse
starts_after=[date/time]will pull offers for candidates expected to start within the designated time frame
candidate_id returned in the response body from step 1, execute the below requests to pull the corresponding application, job, and candidate data that would have been included in the Candidate Hired webhook:
GET Retrieve Candidate to pull candidate data and candidate field values.
The candidate object will include the candidate’s first and last name, contact details, and education info.
GET Retrieve Application to pull application data and application field values.
Application object will include the specific
Opening ID that the candidate has been hired onto (this may correlate with the Requisition/Position ID), the candidate source, and which Greenhouse user that will receive credit for the referral.
GET Retrieve Job to pull job data and job field values.
Job object will include the
Requisition ID and
Opening ID which typically identify the Requisition and/or Position in the HRIS.