⚠️ If you’re already using Javelo and have users in the app, please read Preparing Javelo for External User Source Integration before proceeding.
How to configure the synchronization between BambooHR and Javelo?
BambooHR expose some resources through an HTTP interface that use a Basic Auth based authentication mechanism.
An API key is passed as username whereas the password is not used and may be a random string.
The first thing you have to do is to regenerate this API key on BambooHR, and test it.
For more details, please see BambooHR getting started documentation.
Once done, this token and your subdomain on BambooHR (If you access BambooHR at https://mycompany.bamboohr.com, then the subdomain is "mycompany") will be used to set up the synchronization between Javelo and BambooHR. Please communicate them to your contact at Javelo to proceed with the integration.
What is synchronized with BambooHR?
Attributes
The following BambooHR attributes, that are returned by the "get employee directory" endpoint, are mapped to Javelo:
User List attributes
Name | Mandatory for Javelo | Description |
id | yes | Unique identifier for employee on BambooHR |
firstName | yes | - |
lastName | yes | - |
workEmail | yes | Professional email address of the employee |
jobTitle | no | Current employee's job title |
department | no | Current employee's department |
But additional information are fetched by Javelo, requesting the "get employee" endpoint.
User get attributes
Name | Mandatory for Javelo | Description |
hireDate | no | The date the employee was hired |
terminationDate | no | End of contract date. Please note that this will deactivate the user at date. |
Some other fields may be mapped, please contact us to know more about what is possible to do.