Alooba is a skills assessment platform that helps teams evaluate candidates' skills fairly and efficiently across a range of test types (multiple choice, coding, SQL, one-way video interview and more) and skills.
Alooba's integration with Greenhouse Recruiting lets you invite candidates to Alooba assessments directly from a job's interview plan, and automatically sync each candidate's Alooba results back onto their Greenhouse profile. With the Harvest Advanced API enabled, you can sync back results at a per-skill and per-test level as custom fields, allowing for easy filtering within Greenhouse.
Configure the Alooba integration
Enabling the base integration
See also Greenhouse's own guide to retrieving a partner API key and adding an assessment stage to your interview plan, which covers the Greenhouse-side steps below in more general terms.
Log in to an Owner or Admin account in Alooba, go to Organization Settings, and generate an API key for Greenhouse Assessments. Save it securely — it will not be shown again.
Open a support ticket with Greenhouse Support to connect the key.
Note: Do not send the API key in the initial ticket. Greenhouse Support will reply with a SendSafely link to share it securely.
Once connected, add the Alooba stage to a job's interview plan: go to the job > Job Setup > Interview Plan > Edit Stages > Add Stage > Add from library > select Alooba > Add.
Position the stage where you want it in the hiring process, then click Save.
All configuration of the assessment itself (test content, scoring, cheating-prevention mechanisms, etc.) happens in Alooba directly.
To choose which Alooba test to send for this role, click Edit Interview, then search for the name of the appropriate test, select it, and click Save.
Your assessment is now set up for that role.
Enable the advanced integration with Harvest API (optional)
The Harvest integration enriches candidate profiles in Greenhouse by adding each candidate's Alooba score breakdown as custom fields on their application.
Alooba uses Greenhouse's OAuth sign-in for this.
From your Alooba Organization Settings, click Connect (or Reconnect) Harvest API.
You'll be taken to Greenhouse's sign-in/authorization screen. Log in and approve the requested permissions. If you're a Site Admin, you'll also see an option to authorize using an organization-level service account rather than your individual login — Alooba recommends this so the connection isn't tied to one person's account.
The Alooba page will show Harvest API Connected — no further setup needed. Alooba maintains the connection automatically; you won't need to reconnect unless access is revoked on Greenhouse's side.
Permissions Alooba requests, and why:
| Permission | Why Alooba needs it |
harvest:users:list |
To find the Harvest user your results should be attributed to |
harvest:users:create |
To create that user automatically if one doesn't exist yet |
harvest:custom_fields:list |
To check whether Alooba's result fields already exist |
harvest:custom_fields:create |
To create them automatically if they don't |
harvest:applications:update |
To write the assessment result onto the candidate's application |
Fields Alooba creates and writes to:
| Greenhouse custom field | Source | Written when |
| Overall Alooba score | Candidate's overall assessment result | Assessment completed (updates again if a Free Response test is graded manually afterward) |
| Pass/fail status | Assessment pass/fail outcome | Assessment completed (updates again if a Free Response test is graded manually afterward) |
| Per-subject/test score breakdown | Individual test scores within the assessment | Assessment completed (updates again if a Free Response test is graded manually afterward) |
Exactly which breakdown fields appear depends on how your assessment is configured.
Note: Alooba only writes the custom fields listed above — it never modifies any other field, job, or candidate data in Greenhouse.
If you're already using Alooba's older Harvest API-key integration, reconnecting via OAuth is a one-time action.
Enable candidate status synchronization (optional, webhook-based)
Alooba supports Greenhouse's candidate reject, unreject, hired, and unhired webhooks. These webhooks notify Alooba whenever a candidate is rejected or hired in Greenhouse, so Alooba can update the candidate's status accordingly. This feature is optional — if you choose not to enable it, you can skip the steps below.
To set up candidate status synchronization, add new webhooks from the Webhooks page in the Greenhouse Dev Center. You'll need to add four webhooks, one for each event. The configuration for each webhook is identical except for the Name and When fields. Use one of the following for When on each webhook:
- Candidate or Prospect rejected
- Candidate or Prospect unrejected
- Candidate has been hired
- Candidate has been unhired
Use the values below to configure each webhook:
- Name: a label of your choosing to identify the webhook's purpose (e.g., "Alooba Reject Candidate").
-
Endpoint URL:
https://integration.v2.alooba.com/v1/greenhouse/webhook - When: the event that triggers the webhook — one of the four listed above; repeat this setup for each.
- Secret Key: the Alooba Greenhouse API key generated when setting up the initial assessment integration.
-
Error recipient email:
tech-support@alooba.com, so Alooba is informed of any issues with the webhook.
Additional HTTP headers
Within Advanced settings, add the following header to identify the requesting organization:
X-Organisation: <company-name>
The company name must exactly match the Organization Name field on the Alooba Organization settings page.
Enable Candidate Data Anonymization (optional)
Alooba supports Greenhouse's anonymize candidate webhook. This feature automatically anonymizes candidate data in Alooba whenever a candidate is anonymized in Greenhouse, so Alooba stays aligned with the data retention policies defined in Greenhouse and can honor candidate requests to have their data forgotten.
When a candidate is anonymized in Greenhouse, Greenhouse notifies Alooba via the anonymize webhook. Alooba then automatically anonymizes the corresponding candidate's data in its system by removing the following personally identifiable information (PII) sent from Greenhouse:
- Name
- Email address
- Phone number
- Resume URL
Other PII collected when taking the assessment is also anonymized. This feature is optional — if you choose not to enable it, you can skip the steps below.
To set up the anonymization webhook, add a new webhook from the Webhooks page in the Greenhouse Dev Center. The configuration is exactly the same as candidate status synchronization above, with the exception of the event that triggers the webhook.
Use the values below to configure the webhook:
- Name: a label of your choosing to identify the webhook's purpose (e.g., "Alooba Anonymize Candidate").
-
Endpoint URL:
https://integration.v2.alooba.com/v1/greenhouse/webhook - When: select "Candidate anonymized."
- Secret Key: the Alooba Greenhouse API key generated when setting up the initial assessment integration.
-
Error recipient email:
tech-support@alooba.com, so Alooba is informed of any issues with the webhook.
Additional HTTP headers
Within Advanced settings, add the following header to identify the requesting organization:
X-Organisation: <company-name>
The company name must exactly match the Organization Name field on the Alooba Organization settings page.
Use the Alooba integration with Greenhouse Recruiting
Sending assessment invitations
Move candidates into the Alooba stage using Bulk Actions > Move to Another Stage, or send an individual candidate's test by clicking Send Test next to their stage. If you're sending in bulk, filter by Test Status: To Be Sent first. The test and grader default to what was configured on the Alooba stage.
Once sent, the candidate's stage in Greenhouse Recruiting shows the assessment's status, updating once the candidate completes it.
Accessing assessment results
Once a candidate completes their assessment, their Candidate Interview Kit in Greenhouse shows a link to the submitted assessment. Click Go to test to see the candidate's full results in Alooba.
Day-to-day management of the assessment itself (grading overrides, retakes, etc.) happens in Alooba directly.
If the Harvest integration is enabled, as soon as a candidate completes their Alooba assessment, their assessment status, per-test score, and per-skill score appear as custom fields on their Greenhouse application right away.
Any manual grading you do for free response tests also flows through to the Greenhouse custom fields, typically within a couple of minutes.
Alooba recommends testing end-to-end (invite → complete → check results/sync) before using the integration with real candidates.
Additional resources
For questions or issues with this integration, contact Alooba support at support@alooba.com.