Integrate HiBob ATS with Boon

Last updated: March 3, 2026

Overview

To authenticate Hibob using a Service Account, you will need to provide the following information:

Service Account User ID

Service Account Token

Prerequisites

Please ensure you fulfill all the requirements to set up the integration:

You have Administrator permissions in your company's Hibob instance

⁠⁠⁠

Note: The written instructions below are updated more frequently than our video guide, which may not always reflect the latest changes to Hibob's own user interface.

Instructions

Step 1: Create the Service User in your Hibob Account

1. Navigate to your Hibob System Settings

⁠⁠⁠

CleanShot 2024-12-12 at 14.00.07.png

2. On the Settings screen, open Integrations and click Manage on the Service users tile

⁠⁠⁠

CleanShot 2024-12-12 at 13.41.57.png

3. Click on Create service user

⁠⁠⁠

CleanShot 2024-12-12 at 13.43.10.png

4. Enter any Display name and click Create

⁠⁠⁠

CleanShot 2024-12-12 at 13.44.30.png

5. On the next screen, Hibob display the credentials for your new service user. Make a note of both the ID and the Token, then click on Go to permission groups and proceed with the next step

⁠⁠⁠

CleanShot 2024-12-12 at 13.46.41.png

Step 2: Create a Permission Group

Click Add permission group, then Service user

⁠⁠⁠

CleanShot 2024-12-12 at 13.49.17.png

2. Enter any Group name, select your new service user under Select service users and click Create

⁠⁠⁠

CleanShot 2024-12-12 at 13.50.12.png

3. When asked to confirm the changes, click Confirm

4. Switch to the People's data tab of the new Permission Group, pick "Select people by condition" under Whose data can members access?, then click on Edit to select the people the integration can access

⁠⁠⁠

CleanShot 2024-12-12 at 13.55.13.png

5. In the Select people by condition pop-up, select all relevant Lifecycle Statuses. In most scenarios this will include Hired, Employed, and Terminated. Click Apply twice once done:

⁠⁠⁠

CleanShot 2024-12-12 at 13.55.46.png

6. Back in the People's Data add the following permissions.

Please note the permissions below are the required permissions for the full HRIS API. You only need to configure the permissions based on your use case.

People > Basic Info

View selected employees' Basic info sections (This is required to surface employees)

People > Employment

View selected employees' Employment sections

View selected employees' Employment section histories

People > History

View selected employees' profile changes history

People > Identification

View selected employees' Identification sections

Edit selected employees' Identification sections (only applicable if you want full unobscured SSN numbers.)

People > Lifecycle

View selected employees' Lifecycle sections (This is needed to surface Employment Status)

Edit selected employees' Lifecycle sections

View selected employees' Lifecycle section histories

People > Personal

View selected employees' Personal sections

Edit selected employees' Personal sections (Note: This is needed to surface Date of Birth. We will NOT edit any employee sections)

People > Personal contact details

View selected employees' Personal contact details sections

Edit selected employees' Personal contact details sections

People > Work

View selected employees' Work sections

View selected employees' Work section histories

People > Work contact details

View selected employees' Work contact details sections

7. Once done adding the above permissions, finish creating the Permission Group by selecting Save

Step 3: Link your Hibob account

Copy and paste the Service Account User ID and Token created in part 1 into the linking flow

⁠⁠⁠

Screen Shot 2022-09-23 at 3.28.56 PM.png

​You're done! 🎉

NotesHibob allows moving fields into categories other than those listed in the guide above. If some fields are missing after linking your Hibob account, view a sample employee in Hibob and confirm under which category (e.g. Personal, Work, About) the missing field can be found. Then add View permissions under People's data for that category as described above (for particularly sensitive fields⁠ you would also need to grant Edit permissions so Merge can read the respective field values).

Process complete! 🎉