Visualize BambooHR users and files, map BambooHR users to employees and managers, and monitor changes through queries and alerts.
- Installation guide
- BambooHR data model
For this integration, you will need to generate a REST API key before initiating the integration in JupiterOne. Once the API key has been retrieved, proceed to JupiterOne to continue.
To complete the BambooHR integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select BambooHR. Click New Instance to begin configuring the integration.
Creating an BambooHR instance requires the following:
The Account Name used to identify the BambooHR account in JupiterOne. Ingested entities will have this value stored in
AccountNametoggle is enabled.
Description to assist in identifying the integration instance, if desired.
Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as
DISABLEDand manually execute the integration.
Client Namespace (subdomain) for your BoombooHR account.
The BambooHR API Key generated for use with JupiterOne.
Click Create once all values are provided to finalize the integration.
The users listing API includes user records of employees that have been terminated (
active: false in the User entity). BambooHR employee records also have an
employeeNumber that is assigned when the employee is created and which may later be modified. There is a permanent
id property that does not change and very likely is not equal to the
Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.
The following entities are created:
|Resources||Entity ||Entity |
The following relationships are created:
|Source Entity ||Relationship ||Target Entity |